AbstractSiteMojo.isMaven3OrMore() is an example how to check if you're
running maven 3. In any case, fixing this this would require a release
of doxia-integration-tools-1.5. Or was that planned anyway?
-Lukas
Vincent Latombe wrote:
On my side, I really would like to see MSITE-604 fixed,
Hi Lukas,
I've proposed a second patch only affecting the site-plugin, which reuses
AbstractSiteMojo.isMaven3OrMore()
Vincent
2012/4/23 Lukas Theussl ltheu...@apache.org
AbstractSiteMojo.**isMaven3OrMore() is an example how to check if you're
running maven 3. In any case, fixing this this
On my side, I really would like to see MSITE-604 fixed, I've given it some
thoughts today, and unfortunately I can only fix it for Maven 3, not for
Maven 2 (because of MNG-1943
http://jira.codehaus.org/browse/MNG-1943that is only fixed with
Maven 3). I've proposed a patch that is still work
in
MSITE-601 is a wagon issue IIUC, the other issues can be delayed.
Thanks Denis for doing this!
-Lukas
Robert Scholte wrote:
Hi Dennis,
I don't see any blockers in Jira, only one critical (MSITE-601) but this
seems to be a rare case, so I'd prefer to push that one to a later
release too.
Hi Dennis,
I don't see any blockers in Jira, only one critical (MSITE-601) but this
seems to be a rare case, so I'd prefer to push that one to a later release
too.
MSITE-582 is confirmed by Hervé, an IT has been added.
I'd expect that the new Doxia versions should result in a very enhanced
Hi,
Now that the Doxia releases are done, I'd like to focus on Maven Site
Plugin. We have two pending releases; 2.4 which will be the last release
of the 2.x series and then 3.1.
Looking in JIRA, all the issues scheduled for 2.4 have been fixed and
closed. Does anyone want to add anything more
