[jira] Commented: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor

[ http://jira.codehaus.org/browse/MJAVADOC-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189178#action_189178 ] jcrouvi commented on MJAVADOC-257: -- @Vincent Siveton: With the version 2.2 it works fine with the

[jira] Created: (MJAVADOC-257) maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor

maven-javadoc-plugin 2.5, 2.6 and mojo: Error extracting plugin descriptor -- Key: MJAVADOC-257 URL: http://jira.codehaus.org/browse/MJAVADOC-257 Project: Maven 2.x Javadoc Plugin

[jira] Commented: (MJAVADOC-224) CLONE -If Javadoc is set to aggregate, the build fails inside a Maven plugin module

[ http://jira.codehaus.org/browse/MJAVADOC-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=19#action_19 ] jcrouvi commented on MJAVADOC-224: -- Issue [http://jira.codehaus.org/browse/MJAVADOC-257] added >

[jira] Commented: (MJAVADOC-224) CLONE -If Javadoc is set to aggregate, the build fails inside a Maven plugin module

[ http://jira.codehaus.org/browse/MJAVADOC-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188281#action_188281 ] jcrouvi commented on MJAVADOC-224: -- According to the comment above (jcrouvi added a comment - 24/A

[jira] Commented: (MJAVADOC-224) CLONE -If Javadoc is set to aggregate, the build fails inside a Maven plugin module

[ http://jira.codehaus.org/browse/MJAVADOC-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188279#action_188279 ] jcrouvi commented on MJAVADOC-224: -- I experience the same phenomenon with maven-javadoc-plugin 2.

[jira] Commented: (MRELEASE-389) Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)

[ http://jira.codehaus.org/browse/MRELEASE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156709#action_156709 ] jcrouvi commented on MRELEASE-389: -- I have just tested it again and it works (??). I can not repro

[jira] Updated: (MRELEASE-389) Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)

[ http://jira.codehaus.org/browse/MRELEASE-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] jcrouvi updated MRELEASE-389: - Attachment: jcrouvi_20081204_test.log Test > Properties releaseVersion and developmentVersion are not read

[jira] Commented: (MRELEASE-173) Allow command line specification of versions

[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154963#action_154963 ] jcrouvi commented on MRELEASE-173: -- Issue http://jira.codehaus.org/browse/MRELEASE-389 opened > A

[jira] Created: (MRELEASE-389) Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform)

Properties releaseVersion and developmentVersion are not read correctly during release:prepare (eventually release:perform) --- Key: MRELEASE-389

[jira] Commented: (MRELEASE-173) Allow command line specification of versions

[ http://jira.codehaus.org/browse/MRELEASE-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154950#action_154950 ] jcrouvi commented on MRELEASE-173: -- Hi, Is this bug really closed: * Test environment ** Maven v

[jira] Commented: (MRELEASE-128) SCM properties being replaced during release:perform

[ http://jira.codehaus.org/browse/MRELEASE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154758#action_154758 ] jcrouvi commented on MRELEASE-128: -- Hi, We are still experiencing this problem with the following