On Mon, Feb 11, 2013 at 10:52 AM, Hugo Trippaers <[email protected]> wrote: > >> -----Original Message----- >> From: David Nalley [mailto:[email protected]] >> Sent: Monday, February 11, 2013 4:14 PM >> To: Chip Childers >> Cc: Alex Huang; Hugo Trippaers; [email protected] >> Subject: Re: [DISCUSS] Binary downloads.... >> >> On Mon, Feb 11, 2013 at 10:06 AM, Chip Childers >> <[email protected]> wrote: >> > On Mon, Feb 11, 2013 at 07:00:10AM -0800, Alex Huang wrote: >> >> > This is done automagically. Everytime we do a successful build on >> >> > the ASF Jenkins server the resulting artifacts will be uploaded to the >> >> > ASF >> repository. >> >> > This is controlled by the apache master pom that we include in our >> >> > project. A lot of our artifacts are already there at the moment. We >> >> > only have publisched SNAPSHOT release though as from a maven point >> >> > of view we have not made a release yet I think. (This requires >> >> > triggering a build with a release tag from the Jenkins system afaik). >> >> > >> >> > The main think would be to discuss how we want the artifacts to >> >> > look like. At the moment only the management server is in a shape >> >> > that it can be distributed as a complete entity. Just pick up the >> >> > war file and drop it in some java web container. Works for tomcat and >> jetty at least. >> >> > >> >> >> >> Nice! Thanks Hugo. Then we should be at least be able to make the >> management server war a downloadable option on our website? Even that >> would be nice. >> >> >> >> --Alex >> > >> > I'll try to sort out how to correctly publish 4.1.0-incubating's war >> > file as part of the release process. >> >> I've figured out the maven side of this, just haven't had the cycles to >> document it. >> >> I'm not sure if jenkins will magically publish non-SNAPSHOT artifactos. >> >> --David > > There is some magic in the maven release plugin. So far I haven't been able > to test or use it. But according to specs it should automagically create a > signed release, strip the -SNAPSHOT part and publish the release on the > listed artifact server. The artifact server will recognize that it is a > release (or actually that it is not a snapshot) and make it available on the > release artifact store.
Yeah - there is something in the release plugin that does this. --David
