+1 - we need a better solution! Can we import old releases (at least the 1.3.X and the 1.4-RCX releases)?
-- Jeremy Thomerson http://www.wickettraining.com On Sat, Jun 27, 2009 at 6:46 PM, Igor Vaynberg<[email protected]> wrote: > +1 > > we release to nexus at my work and it is as simple as mvn > release:deploy to get all the artifacts into the repo. > > -igor > > On Sat, Jun 27, 2009 at 12:43 PM, Martijn > Dashorst<[email protected]> wrote: >> +1 >> >> On Sat, Jun 27, 2009 at 9:24 PM, Martijn >> Dashorst<[email protected]> wrote: >>> We've been releasing to people.apache.org, and that is/was painful for >>> the maven repository artifacts: we loose metadata with each release. >>> Some of the maven guys work for sonatype and have donated the Nexus >>> enterprise repository to the ASF for our releases. I'd like to propose >>> that we release all future releases through the nexus repository >>> instead of people.apache.org. (I expect this to become policy >>> somewhere in the future). >>> >>> Here is what the Maven Project is using if you want to understand what >>> you would need to do as a project: >>> >>> http://maven.apache.org/developers/release/releasing.html >>> >>> http://maven.apache.org/developers/committer-settings.html >>> >>> There is also the staging documentation in the Nexus book: >>> >>> http://www.sonatype.com/books/nexus-book/reference/staging.html >>> >>> Also know that using Nexus requires us to take your artifacts off >>> people.apache.org and place them under the management of Nexus. But >>> once this is done, staging and promoting is painless and we will fully >>> manage the repository (including snapshot management) and the sync >>> artifacts to central for you. >>> >>> [ ] yes, use nexus deployment from now >>> [ ] no, ... >>> >>> Martijn >>> >> >> >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> Apache Wicket 1.3.5 is released >> Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. >> >
