Yeah, I'll add SNAPSHOTs for the 1.x branch while I'm at it. It's already being built by Hudson, so it shouldn't be that much trouble to add it. Raised a JIRA for the infrastructure team to get Nexus access for Apache Camel (https://issues.apache.org/jira/browse/INFRA-1950)
Regards, Gert Vanthienen ------------------------ Open Source SOA: http://fusesource.com Blog: http://gertvanthienen.blogspot.com/ 2009/3/24 Willem Jiang <willem.ji...@gmail.com>: > +1, and we need to setup a same deployment for Camel 1.x. > > Willem > > > Claus Ibsen wrote: >> +1 >> >> Would that apply for both Camel 1.x and trunk? >> >> AFAIR we don't have SNAPSHOT builds of 1.x published any more, >> requested by end users to be published again. >> >> >> On Mon, Mar 23, 2009 at 8:52 PM, Gert Vanthienen >> <gert.vanthie...@gmail.com> wrote: >>> L.S., >>> >>> >>> Right now, we have two build servers: >>> - Camel builds for deploying nightly snapshots are running on >>> http://projects.open.iona.com/builds/status >>> - Camel builds are running fine on hudson.zones.apache.org for a few weeks >>> now >>> >>> Apache also has a Nexus repository manager installed at >>> http://repository.apache.org now. >>> I'd like to start deploying our SNAPSHOTs to this repository from >>> Hudson directly instead of using the separate build server. In the >>> future, we should also be able to leverage Nexus for the release >>> process as well, i.e. deploy the artifacts under vote to a Nexus >>> staging repo and then just promote the artifacts into the release repo >>> after teh vote. >>> >>> The major downside would be that the repository url for snapshots >>> would change from >>> http://people.apache.org/repo/m2-snapshot-repository/ to >>> https://repository.apache.org/content/repositories/snapshots. >>> >>> >>> Regards, >>> >>> Gert Vanthienen >>> ------------------------ >>> Open Source SOA: http://fusesource.com >>> Blog: http://gertvanthienen.blogspot.com/ >>> >> >> >> > >
