Re: [rt-pmc] Re: [jetty-dev] jetty dependency's and 'releasing' within

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

> Interestingly my Eclipse-centric point of view held that stuff from
> eclipse.org was much more trusted in this regard. The management policies
> for the maven repo are unknown to me.  It might be interesting to see if the
> Eclipse foundation/community could come to trust the maven repo and
> infrastructure.  Until such time it seems implausible that eclipse.org would
> ship bytes that come from an "as yet" untrusted source on a regular basis
> without review.  It is much more realistic to say that projects identify
> bytes they want to ship, get them cleared and then host them on eclipse.org.
>

I suspect the route here is to have eclipse prepare a maven repository
following some naming convention that will mesh well with the maven
central repository...and then have the join the many other
repositories that aggregate together into the maven central
repository.  Maven users (like jetty!) would then simply reference
these artifacts in maven central and we should be in good shape.

imo, the servlet-api as it exists as a eclipse bundle would slot into
the maven repo something like...

http://repo2.maven.org/maven2/javax/servlet/servlet-api/2.5.0.v200806031605/servlet-api-2.5.0.v200806031605.jar

however I would be +1 for having eclipse somehow indicated in that
version string... maybe 2.5.0.v200806031605-E

> Is all this captured in the POM?  Is anything else needed other than more
> data in there
>

http://repo2.maven.org/maven2/javax/servlet/servlet-api/2.5.0.v200806031605/servlet-api-2.5.0.v200806031605-javadoc.jar
http://repo2.maven.org/maven2/javax/servlet/servlet-api/2.5.0.v200806031605/servlet-api-2.5.0.v200806031605-sources.jar

^^^^ the javadoc and sources are published alongside the artifact.


> As mentioned, I'm not sure it is an option.  AFAIK eclipse only ships
> approved stuff.  Incubating is the only way we have of marking something as
> "not quite up to normal standards".  The IP team might be able to advise.
>  Perhaps there is something I'm missing.
>

So its painfully clear, the jetty7 release we are talking about is
only the distribution that end users download and use...we have
limited support for an update site and need to invest more time then
we have had to improve that setup and be more comfortable having our
update site contain anything more then the most basic jetty server and
client....peer review on that update site is more then welcome :)

so I would hope we would be able to be granted an exemption for us to
include these 2 jsp jar files and a cometd example war file into that
distribution people download....imo pointing over to codehaus for a
couple of artifacts and some instructions on putting them in the right
places in the distribution is a cruddy solution which we'll do as a
last resort...

> Yeah, I suggest identify the end goal and then full steam ahead.  IMHO the
> end goal is Jetty core with JSP support shipping from Eclipse.org in June
> 2010 all CQ'd and tidy.

The timeline we are chasing here is end of July/August 2009....within
the month basically...

cheers,
jesse