[jira] (DOXIATOOLS-36) doxia-maven-plugin:1.2 fails with NoClassDefFoundError

[ https://jira.codehaus.org/browse/DOXIATOOLS-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg moved DOXIA-432 to DOXIATOOLS-36: - Fix Version/s: (was: 1.3) doxia-book-

[jira] (DOXIA-465) Move doxia-book and doxia-maven-plugin to Doxia Tools

Dennis Lundberg created DOXIA-465: - Summary: Move doxia-book and doxia-maven-plugin to Doxia Tools Key: DOXIA-465 URL: https://jira.codehaus.org/browse/DOXIA-465 Project: Maven Doxia Issue Ty

[jira] (DOXIA-465) Move doxia-book and doxia-maven-plugin to Doxia Tools

[ https://jira.codehaus.org/browse/DOXIA-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed DOXIA-465. - Resolution: Fixed Fix Version/s: 1.3 Assignee: Dennis Lundberg Fixed in [r1307847|http

[jira] (MSHARED-219) Maven3 LinkageError in maven report

[ https://jira.codehaus.org/browse/MSHARED-219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MSHARED-219: -- Description: Creating a maven report using some kind of a filter sink: {code:java}public class Dox

[jira] (MSKINS-47) $headContent can be undefined when using an older doxia-site-renderer

Robert Scholte created MSKINS-47: Summary: $headContent can be undefined when using an older doxia-site-renderer Key: MSKINS-47 URL: https://jira.codehaus.org/browse/MSKINS-47 Project: Maven Skins

[jira] (MSKINS-47) $headContent can be undefined when using an older doxia-site-renderer

[ https://jira.codehaus.org/browse/MSKINS-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSKINS-47. Resolution: Fixed Fix Version/s: fluido-1.2.2 Assignee: Robert Scholte Fixed in [rev. 131

[jira] (MNG-5271) Cannot resolve active profile name at build time

Richard Bone created MNG-5271: - Summary: Cannot resolve active profile name at build time Key: MNG-5271 URL: https://jira.codehaus.org/browse/MNG-5271 Project: Maven 2 & 3 Issue Type: Bug

[jira] (MENFORCER-118) DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion

[ https://jira.codehaus.org/browse/MENFORCER-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296120#comment-296120 ] Raman Gupta commented on MENFORCER-118: --- Of course, the other question is: why does Maven

[jira] (MENFORCER-118) DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion

[ https://jira.codehaus.org/browse/MENFORCER-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296123#comment-296123 ] Raman Gupta commented on MENFORCER-118: --- In the meantime, until this is fixed I have forke

[jira] (MENFORCER-118) DependencyConvergence gets better if it doesn't fail on snapshots of same baseVersion

[ https://jira.codehaus.org/browse/MENFORCER-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Raman Gupta updated MENFORCER-118: -- Attachment: menforcer-118.patch Patch as suggested by OP. > DependencyConvergenc

[jira] (MSITE-627) Upgrade to reporting-exec 1.0.2

[ https://jira.codehaus.org/browse/MSITE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MSITE-627: -- Issue Type: Task (was: Improvement) Summary: Upgrade to reporting-exec 1.0.2 (was: upgrade to

[jira] (MSITE-627) Upgrade to reporting-exec 1.0.2

[ https://jira.codehaus.org/browse/MSITE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296127#comment-296127 ] Dennis Lundberg commented on MSITE-627: --- Upgrade to released version of maven-reporting-exec i