With the 3.0.1 version of our master POM, I've never been able to run a
release without retries. This seems to have been caused partly by issues
in the Maven release plugin, partly by suboptimal configuration.
There is now a new version org.ops4j:master:3.1.0, already on Maven
Central, which hopefully solves all these issues.
To run a fully automatic release, include the following profile in your
Maven _installation_ settings (not the user settings.xml which are
overridden by the Maven Release Plugin):
<profile>
<id>sonatype-oss-release</id>
<properties>
<gpg.passphrase>mysecretpassphrase</gpg.passphrase>
</properties>
</profile>
This should be sufficient to run an unattended
mvn release:prepare release:perform
For the tag names, I reverted to the default of [artifactId]-[version],
as GitHub builds the file name for download ZIPs from the tag, and it's
not so nice to have a bunch of v2.5.3.zip files in your download folder
where the archive name doesn't indicate the contents.
In addition, I upgraded most plugins to the current version (in
particular, for some fixes and new features in the surefire and resource
plugins).
The pluginManagement section now contains some more general interest
plugins and m2e lifecycle definitions that were used by at least two
different Pax projects.
For testing the new master, I built a real release of Pax JDBC with it,
I staged and reverted a Pax CDI release, and I locally built Pax Exam
and Pax Web with the new parent, all of which were ok, so I hope this
master version works for all other OPS4J projects too.
Best regards,
Harald
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
