Thanks for the pointers Chris! Unfortunately, since we are not a Java project and don't use Maven except for building and deploying our artifacts, releasing artifacts isn't quite as straight forward as I thought it would be at first.
Writing a Maven pom that works with our autotools build system took me quite a while for the 0.9.0-incubating release. The Mesos jar that our build system produces is not sufficient to simply upload it as our artifact. I remember I spent quite a bit of time trying to get it to include everything that is required but then reverted to having Maven rebuild the artifact itself. As Vinod reported in his comment on https://issues.apache.org/jira/browse/MESOS-398, It looks like something has changed since 0.9.0 so that the instructions, which I wrote, are working any more (or maybe I missed something when I wrote the instructions<https://github.com/apache/mesos/blob/trunk/src/java/MESOS-MAVEN-README>down). I'm looking into it now. if anybody else knows of a cleaner process than what we're doing now, or would like to own this I'm happy to hand it over :) Andy On Sun, Jun 2, 2013 at 7:21 PM, Mattmann, Chris A (398J) < [email protected]> wrote: > Hey Guys, > > I can help with this too. Publishing to Maven Central is a snap. > > 1. Make sure there is a mess project on repository.apache.org > (if there isn't, file an INFRA ticket to create one and select > Nexus as the component). > > 2. Once project is available per #1, update the pom.xml for > the project to inherit from the apache pom (latest version was 9 > at one point, may be later version now). > > 3. Doing #2 gives us the ability to run: > mvn release:prepare > mvn release:perform > > 4. This should publish to repository.apache.org as a staging repository. > 5. Then simply log on to http://repository.apache.org and > a. "Close" the staging repository - this creates a reviewable link > to the staging repository that we can paste into our release emails > 6. Once the VOTE thread for the release passes, log back into > http://repository.apache.org > and "Release" the staging repository. This will cause a sync to the > Central repo and all to be well :) > > See full instructions for the OODT project, here: > > https://cwiki.apache.org/confluence/display/OODT/Release+Process > > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > -----Original Message----- > From: Matei Zaharia <[email protected]> > Reply-To: "[email protected]" <[email protected] > > > Date: Sunday, June 2, 2013 6:08 PM > To: "[email protected]" <[email protected]> > Cc: Andy Konwinski <[email protected]> > Subject: Publishing Mesos to Maven > > >Just FYI, it looks like the last version of the Mesos Java API on Maven > >central is 0.9.0: > >http://mvnrepository.com/artifact/org.apache.mesos/mesos. It would be > >great to get new releases on there so that external projects can link to > >them. I believe Andy published that one to Maven central -- Andy, can you > >explain how you did that, or can someone else from the team do it? (E.g. > >do you guys publish them internally inside Twitter?) I believe it's not > >too bad given the existing POM. > > > >Matei > >
