Hi Andreas,
some comments and questions:
(a) +1. All that is left in the Pax master seems to be outdated.
(b) +1 for 2.0.0.
I did a quick review of the Über-Master [3] and compared the plugin
versions with the latest ones on Maven Central. This is what I noticed:
(c) The CI URL http://ci.ops4j.org/ is broken. So either this is a
redirect you missed in your cleanup, or the entry should be updated.
(d) Is the repos.ops4j profile still required? If so, what for?
(e) Plugin version check:
maven-dependency-plugin 2.3 - Cool, we're ahead of
http://maven.apache.org/plugins/index.html !
This is a list of potential updates with the latest versions from Maven
Central:
maven-jar-plugin 2.3.2
maven-release-plugin 2.2.1
maven-checkstyle-plugin 2.7
wagon-ssh-external 1.0
cobertura-maven-plugin 2.5.1
maven-javadoc-plugin has 2.8 in <pluginManagement> but 2.6.1 in
<reporting>, I'd suggest 2.8 for both.
(f) I don't see what the ops4j.gpg.use-agent property is for, not even
after reading the maven-gpg-plugin docs. Where do you get this agent
from, how do you use it, and when do you have to use it?
(g) For the benefit of all Eclipse/m2e users - including myself ;-) - I
would like to add an org.eclipse.m2e:lifecycle-mapping section in
<pluginManagement> for all plugins defined in the master POM that are
not recognized by m2e by default.
This will guarantee that m2e can import projects into Eclipse without
error markers and save users manual configuration. There will be no
side-effects on Maven CLI builds or other IDEs.
See [1] for the background and [2] for an example from Pax Exam. I think
the master POM is the best place for this to avoid repetitions in
individual projects.
(h) Does this version already include all the changes you were planning
to do to make the next Pax Runner release work more smoothly? If
anything is missing, I'm ready to help out...
Best regards,
Harald
[1] http://wiki.eclipse.org/M2E_plugin_execution_not_covered
[2] https://github.com/ops4j/org.ops4j.pax.exam2/blob/master/pom/pom.xml
[3] https://github.com/ops4j/org.ops4j.master/blob/master/pom.xml
Am 31.08.2011 13:39, schrieb Andreas Pieber:
OK, finally in my lunch break I had some time to revisite this:
(a) currently we have an ueber master AND a pax master [1] I think we
should completely remove it.
(b) I've refactored great parts of the ueber master and upgraded almost
all versions there --> I think we should upgrade the version to 2.0.0
since the svn/scm parts had been completely removed.
WDYT?
Kind regards,
Andreas
[1] https://github.com/ops4j/org.ops4j.pax.master/blob/master/pom.xml
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
