servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Baptiste Onofré" ...@nanthrax.net>
Subject Re: [QUESTION] How to deploy an required artifact on repository.apache.org ?
Date Wed, 16 Dec 2009 05:59:54 GMT
Hi Chris,

OK, I will upgrade to Jetty 6.1.22 tonight for the next release. Once released, I will upgrade
to jetty 7 snapshot to begin tests.

Regards
JB
-----Original Message-----
From: Chris Custine <chris.custine@gmail.com>
Date: Tue, 15 Dec 2009 16:09:12 
To: <dev@servicemix.apache.org>; <jb@nanthrax.net>
Subject: Re: [QUESTION] How to deploy an required artifact on 
	repository.apache.org ?

As of Jetty 7 (the eclipse releases), they are deploying under the
org.eclipse.jetty groupId so the newer artifacts are here:
http://repo2.maven.org/maven2/org/eclipse/jetty/aggregate/jetty-all and they
use the date in the version like all of the other Eclipse projects so
7.0.1.v20091125
is the latest version.

Has anyone done any significant testing with the 7.0 releases?  I was
preparing to upgrade to Jetty 6.1.22 in order to get the latest security
fixes but I'm not sure if we should move to 7.0 until after the upcoming
releases (so that we can get more testing with SNAPSHOTs post release).

Chris

--
Chris Custine
FUSESource :: http://fusesource.com
My Blog :: http://blog.organicelement.com
Apache ServiceMix :: http://servicemix.apache.org
Apache Directory Server :: http://directory.apache.org


On Tue, Dec 15, 2009 at 1:56 PM, Jean-Baptiste Onofré <jb@nanthrax.net>wrote:

> Hi all,
>
> I would like to upgrade SMX resources (especially component) to Jetty 7.0.1
> (see SMXCOMP-622).
>
> If I go to http://dist.codehaus.org/jetty/, I'm able to see the jetty
> 7.0.1 distribution.
>
> But, if I go to:
> http://repository.apache.org or http://repo1.maven.org I can only see
> jetty 6.1.22 or 7.0.0.pre5 but not the released 7.1.0 version.
>
> As I can deploy the jetty 7.1.0 artifacts myself, how and who I can request
> for that ?
>
> The other way is to deploy in the svn m2-repo but I want to avoid it.
>
> Thanks
> Regards
> JB
>

Mime
View raw message