Mark,
I noticed Benjamin already responded to a few of your questions, so let me just answer the open issues: > The 324 WhitespaceAround errors are generics syntax errors since > mojo-parent uses maven-checkstyle-plugin:2.2 for reports, which in > turn uses Checkstyle 4.x, which does not support Java5 syntax. If I > upgrade this to 2.5 then we have 14 errors, 10 of which are due to > using a MIT license rather than the ASL one. I'll commit this to > mojo-parent. This is weird: mojo-parent[1] uses maven-checkstyle-plugin:2.5 in the build-section, but 2.2 in the reporting-section. These should be the same and would explain the problem. [1] http://svn.codehaus.org/mojo/trunk/mojo/mojo-parent/pom.xml > > - FAQ has a reference to http://jira.codehaus.org/browse/MCOMPILER-75 . This > > issue is closed as 'fixed', which could suggest that this might be one of > > the final heartbeats of this plugin. What's your idea on this one? > > maven-compiler-plugin is the way to go in future but it can only be > used with Java6+. apt-maven-plugin supports Java5. It is also > missing a couple of features: being able to specify processor > dependencies within the plugin dependencies rather than the exported > project dependencies; and staleness checking [1]. It is also being > used by several projects and so cannot be retired yet. > > [1] > http://mojo.codehaus.org/apt-maven-plugin/examples/configuring-staleness-checking.html I think you should mentioned this. If there's any doubt, just sum these facts to confirm the apt-maven-plugin is still useful > > btw, it seems like you managed to bypass MSITE-459. It's a pretty deep > > transitive dependency which causes the trouble, but it looks like it's > > solved in the core (still SNAPSHOT). It can take a while before this solved > > in the m-site-plugin as well, so I'd suggest you add this to the mojo-parent > > as well. > > Looks like the real fix will be upgrading wagon-webdav to 1.0-beta-7 > in mojo-parent, see WAGON-60. Not sure when this is planned to be > released, but there's only two issues left that are targeted for this > version. So I can either add my maven-site-plugin workaround to > mojo-parent or we can wait for wagon 1.0-beta-7 to be released? Right now Mojo-developers have to modify their project if they want to do a site-deploy. The mojo-parent doesn't work out-of-the-box anymore where it should. So I'd suggest to fix this with the exclusion. I'll have another look at it and start a vote next week, so developers can use the parent as they used to, apart from the staging of course. > > These are all minor issues which can easily be addressed in the next > version, especially as this is an alpha release. If you're not +1 are > you vetoing this release? Nope, I didn't say -1, since it's still a prerelease version. Also be aware that you didn't mention how the vote will pass. I *assume* lazy consensus, since that's what often happens, but I don't think that's the default-value ;) - Robert
