Hey Harald, On Tue, Aug 30, 2011 at 23:55, Harald Wellmann <harald.wellm...@gmx.de>wrote:
> Hi Admins, > > a new Pax URL release is on its way and should be reaching Maven Central > with the next sync. Things went more or less smoothly as described in the > README. > > The only problem I'm aware of so far is entirely my own mistake: I missed > changing the default version suggested by the Maven Release plugin, so this > will be a 1.3.5 version instead of the 1.4.0 we had agreed on. > Sorry about that - of course I'm ready to clean this up, but as we cannot > withdraw anything from Maven Central, I wonder if this 1.3.5 version would > really be a problem for anyone - the new "reference:" protocol handler is > just an addition and does not change anything for existing protocol > handlers. So maybe the best thing to do is: relax... > I'm with Toni here; 1.3.5 wont break anything --> no problem :-) > > Another question: What is causing the release process to require so many > manual steps? I've worked with Sonatype OSS repositories in other projects, > where a one-liner "mvn release:prepare release:perform" would simply do the > job. Is it Github, or what's the big difference in Pax from other > projects...? > This is because the master-pom still referencing the site you've no permission on :-( I wanted to fix this for the next release, but well you were faster :-) Basically it should be as simple as removing the site-deploy from the master pom (already on github). If you like we can also do this together for the pax-runner release (feel free to ping me on skype or google talk). Kind regards, Andreas > > Best regards, > > Harald > > > > ______________________________**_________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/**mailman/listinfo/general<http://lists.ops4j.org/mailman/listinfo/general> >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
