[jira] Commented: (MNG-3685) Dependency can't be resolved but has been found in the reactor.

[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199689#action_199689 ] Anthony Whitford commented on MNG-3685: --- I seem to be experiencing this problem with the latest J

[jira] Commented: (MJAVADOC-276) Initial builds of a multi-module project fail

[ http://jira.codehaus.org/browse/MJAVADOC-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199687#action_199687 ] Anthony Whitford commented on MJAVADOC-276: --- Is this related to MNG-3685 or MJAVADOC-116?

[jira] Created: (MJAVADOC-276) Initial builds of a multi-module project fail

Initial builds of a multi-module project fail - Key: MJAVADOC-276 URL: http://jira.codehaus.org/browse/MJAVADOC-276 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.6.1

[jira] Commented: (MCHANGES-149) -DfromDeveloperId does not work if developers are setted in the parent pom

[ http://jira.codehaus.org/browse/MCHANGES-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199672#action_199672 ] Alexandre Navarro commented on MCHANGES-149: Ok thanks. I will test it. > -DfromDevelo

[jira] Commented: (MJAR-20) Don't create empty jars

[ http://jira.codehaus.org/browse/MJAR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199659#action_199659 ] Alexandre Navarro commented on MJAR-20: --- Some news of including this patch in the next release? A

[jira] Commented: (MCHANGES-173) Failed to generate report when version is not the last schedule.

[ http://jira.codehaus.org/browse/MCHANGES-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199654#action_199654 ] Christophe Lallement commented on MCHANGES-173: --- Hi Dennis, All release together we

[jira] Commented: (MJAR-132) Test jar is generated on mvn install or deploy when the type of artifact is pom (and herited by a parent pom)

[ http://jira.codehaus.org/browse/MJAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199652#action_199652 ] Alexandre Navarro commented on MJAR-132: You can close it because it is duplicate with http://

[jira] Closed: (MECLIPSE-622) mvn eclipse:eclipse fails or doesn't generate proper .classpath when specifying the same resource directory with different filtering rules

[ http://jira.codehaus.org/browse/MECLIPSE-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pascal Thivent closed MECLIPSE-622. --- Resolution: Duplicate > mvn eclipse:eclipse fails or doesn't generate proper .classpath when > s

[jira] Created: (MECLIPSE-622) mvn eclipse:eclipse fails or doesn't generate proper .classpath when specifying the same resource directory with different filtering rules

mvn eclipse:eclipse fails or doesn't generate proper .classpath when specifying the same resource directory with different filtering rules -- Ke

[jira] Commented: (MJAR-132) Test jar is generated on mvn install or deploy when the type of artifact is pom (and herited by a parent pom)

[ http://jira.codehaus.org/browse/MJAR-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199649#action_199649 ] Alexandre Navarro commented on MJAR-132: The problem exists also you package the parent pom. >

[jira] Closed: (MCHANGES-136) Amend (HTML) docs to reflect new features introduced with release 2.1

[ http://jira.codehaus.org/browse/MCHANGES-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-136. Resolution: Not A Bug All xml elements and attributes are described on this page: http://maven.

[jira] Closed: (MCHANGES-152) page encoding ISO-8859-1 not definable

[ http://jira.codehaus.org/browse/MCHANGES-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-152. Resolution: Not A Bug > page encoding ISO-8859-1 not definable > --

[jira] Closed: (MCHANGES-135) JIRA links on changes report are broken

[ http://jira.codehaus.org/browse/MCHANGES-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-135. Resolution: Fixed Fix Version/s: 2.3 Assignee: Dennis Lundberg The URL to the i

[jira] Commented: (MCHANGES-155) When an empty element is present in changes.xml the parser fails

[ http://jira.codehaus.org/browse/MCHANGES-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199605#action_199605 ] Martin Vysny commented on MCHANGES-155: --- I just wanted the "Issue 9966" text to appear as act

[jira] Commented: (MCHANGES-149) -DfromDeveloperId does not work if developers are setted in the parent pom

[ http://jira.codehaus.org/browse/MCHANGES-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199603#action_199603 ] Dennis Lundberg commented on MCHANGES-149: -- That needs to be {noformat} -Dchanges.fromDeve

[jira] Closed: (MCHANGES-182) Plugin seems to be tied to Sun JDK

[ http://jira.codehaus.org/browse/MCHANGES-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-182. Resolution: Duplicate > Plugin seems to be tied to Sun JDK > --

[jira] Commented: (MCHANGES-173) Failed to generate report when version is not the last schedule.

[ http://jira.codehaus.org/browse/MCHANGES-173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199599#action_199599 ] Dennis Lundberg commented on MCHANGES-173: -- You are probably hitting the limit of max 25 i

[jira] Commented: (MCHANGES-155) When an empty element is present in changes.xml the parser fails

[ http://jira.codehaus.org/browse/MCHANGES-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199598#action_199598 ] Dennis Lundberg commented on MCHANGES-155: -- The parser is generated by Modello. Will need

[jira] Commented: (MCHANGES-140) Create an announcement check mojo

[ http://jira.codehaus.org/browse/MCHANGES-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199596#action_199596 ] Dennis Lundberg commented on MCHANGES-140: -- I like this, it adds one more level of checkin

[jira] Closed: (MCHANGES-153) For multi-module project, sending the email once for the project, not one email for each sub-module

[ http://jira.codehaus.org/browse/MCHANGES-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-153. Resolution: Duplicate > For multi-module project, sending the email once for the project, not o

[jira] Closed: (MCHANGES-131) It would be nice if the announcement plugin bound to the validate phase to make sure changes.xml exists and has the proper versions in it.

[ http://jira.codehaus.org/browse/MCHANGES-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-131. Resolution: Not A Bug The announcement goals are not bound to any phase by default. That's beca

[jira] Closed: (MCHANGES-187) If jiraMerge=true then releases that are only in JIRA will not be included in the announcement

[ http://jira.codehaus.org/browse/MCHANGES-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-187. Resolution: Fixed Fix Version/s: 2.3 Assignee: Dennis Lundberg Fixed in [r88457

[jira] Created: (MCHANGES-187) If jiraMerge=true then releases that are only in JIRA will not be included in the announcement

If jiraMerge=true then releases that are only in JIRA will not be included in the announcement -- Key: MCHANGES-187 URL: http://jira.codehaus.org/browse/MCHANGES-187

[jira] Closed: (MCHANGES-145) Make it possible to run the announcement goals only once for a multi-module project

[ http://jira.codehaus.org/browse/MCHANGES-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-145. Resolution: Fixed I opted for a different approach than the attached patch. This is based on th

[jira] Commented: (MCHANGES-150) [regression] Report Sets not honored during site goal

[ http://jira.codehaus.org/browse/MCHANGES-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199588#action_199588 ] Dennis Lundberg commented on MCHANGES-150: -- I can confirm that this is a regression betwee

[jira] Closed: (MCHANGES-186) Issue links for JIRA are broken when using the %URL% token

[ http://jira.codehaus.org/browse/MCHANGES-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGES-186. Resolution: Fixed Fix Version/s: 2.3 Assignee: Dennis Lundberg Fixed in [r88455

[jira] Updated: (MCHANGES-145) Make it possible to run the announcement goals only once for a multi-module project

[ http://jira.codehaus.org/browse/MCHANGES-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg updated MCHANGES-145: - Fix Version/s: 2.3 Assignee: Dennis Lundberg Issue Type: New Feature (was: Bu

[jira] Closed: (MINSTALL-71) localRepositoryPath ignored

[ http://jira.codehaus.org/browse/MINSTALL-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rémi Perrot closed MINSTALL-71. --- Resolution: Fixed Fix Version/s: 2.3 I test with 2.3 version and it works as intended > localRepos

[jira] Created: (MINSTALL-71) localRepositoryPath ignored

localRepositoryPath ignored --- Key: MINSTALL-71 URL: http://jira.codehaus.org/browse/MINSTALL-71 Project: Maven 2.x Install Plugin Issue Type: Bug Components: install:install-file Affects Versions: 2.2

[jira] Commented: (MNG-4354) DefaultArtifactResolver has problems when used with multiple repos

[ http://jira.codehaus.org/browse/MNG-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199542#action_199542 ] Nicolas Dumoulin commented on MNG-4354: --- I can confirm this annoying bug. For instance, our fix i