[jira] Closed: (MPLUGIN-156) Stabilize ordering of configuration and requirements in generated plugin descriptor

[ http://jira.codehaus.org/browse/MPLUGIN-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPLUGIN-156. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.5.1 Done in [r8

[jira] Created: (MPLUGIN-156) Stabilize ordering of configuration and requirements in generated plugin descriptor

Stabilize ordering of configuration and requirements in generated plugin descriptor --- Key: MPLUGIN-156 URL: http://jira.codehaus.org/browse/MPLUGIN-156 Project: Maven 2

[jira] Closed: (MJAVADOC-251) Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of config injection

[ http://jira.codehaus.org/browse/MJAVADOC-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MJAVADOC-251. -- Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.6.1 Fixed in

[jira] Created: (MJAVADOC-251) Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of config injection

Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of config injection -- Key: MJAVADOC-251 URL: http://jira.codehaus.org/browse/MJAVADOC-251

[jira] Closed: (MNG-4279) wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.

[ http://jira.codehaus.org/browse/MNG-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey closed MNG-4279. --- Resolution: Fixed added code to check that the protocol-provider hint exists before blindly passing it back. If it d

[jira] Commented: (MNG-4162) Removal of all reporting logic from the core of Maven

[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185792#action_185792 ] Olivier Lamy commented on MNG-4162: --- The approach used creating for each report plugin : creating a n

[jira] Commented: (SUREFIRE-118) Cannot override read-only parameter: classpathElements

[ http://jira.codehaus.org/browse/SUREFIRE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185789#action_185789 ] David Hoffer commented on SUREFIRE-118: --- Is it possible to specify the classpath load order o

[jira] Commented: (MNG-4162) Removal of all reporting logic from the core of Maven

[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185780#action_185780 ] Olivier Lamy commented on MNG-4162: --- I have commit stuff in core branch. No big chance only new metho

[jira] Updated: (MNG-4279) wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.

[ http://jira.codehaus.org/browse/MNG-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Casey updated MNG-4279: Assignee: John Casey Description: Currently, if the server section of the settings.xml uses wagonProvide

[jira] Commented: (MSITE-210) DoxiaFilter does not set output encoding

[ http://jira.codehaus.org/browse/MSITE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185776#action_185776 ] Darius commented on MSITE-210: -- I see good output with version 2.1-SNAPSHOT, thanks. > DoxiaFilter does

[jira] Created: (MNG-4279) wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.

wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available. Key: MNG-4279

[jira] Commented: (MSTAGE-7) Unable to use archiva as http source with maven-stage-plugin

[ http://jira.codehaus.org/browse/MSTAGE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185770#action_185770 ] Jacob Robertson commented on MSTAGE-7: -- I'm pretty sure this issue applies to the latest version o

[jira] Commented: (MJAVADOC-246) ExceptionInInitializerError

[ http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185759#action_185759 ] Malachi de AElfweald commented on MJAVADOC-246: --- 2.6-SNAPSHOT does appear to have fix

[jira] Updated: (MENFORCER-81) Create a banned plugins rule

[ http://jira.codehaus.org/browse/MENFORCER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marvin Froeder updated MENFORCER-81: Attachment: banned-plugin.patch Add missing file > Create a banned plugins rule >

[jira] Created: (MENFORCER-81) Create a banned plugins rule

Create a banned plugins rule Key: MENFORCER-81 URL: http://jira.codehaus.org/browse/MENFORCER-81 Project: Maven 2.x Enforcer Plugin Issue Type: New Feature Components: Standard Rules Affects Version

[jira] Commented: (MSITE-420) Parent project site descriptor menu options always a link back to parent site

[ http://jira.codehaus.org/browse/MSITE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185742#action_185742 ] EJ Ciramella commented on MSITE-420: Hmm - that seems to work if it's a parent/child like this (wh

[jira] Commented: (MJAVADOC-249) javadoc:fix should wrap existing comments in

[ http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185729#action_185729 ] Vincent Siveton commented on MJAVADOC-249: -- I guess we could add them (patch welcome!) but

[jira] Commented: (MJAVADOC-247) location of doc-files is wrong on page http://maven.apache.org/plugins/maven-javadoc-plugin/examples/test-javadocs.html

[ http://jira.codehaus.org/browse/MJAVADOC-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185731#action_185731 ] Vincent Siveton commented on MJAVADOC-247: -- Could you provide a patch or reformat your iss

[jira] Commented: (MJAVADOC-250) javadoc:fix mojo should fully qualify {...@link} class names

[ http://jira.codehaus.org/browse/MJAVADOC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185728#action_185728 ] Vincent Siveton commented on MJAVADOC-250: -- Yes we could have the import list but in my sa

[jira] Updated: (MJAVADOC-244) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled

[ http://jira.codehaus.org/browse/MJAVADOC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-244: - Priority: Minor (was: Major) > Javadoc plugin: java files under src/main/javadoc and doc-fil

[jira] Commented: (MJAVADOC-244) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled

[ http://jira.codehaus.org/browse/MJAVADOC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185727#action_185727 ] Vincent Siveton commented on MJAVADOC-244: -- Confirmed. I guess we could add a filter for

[jira] Updated: (MJAVADOC-244) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled

[ http://jira.codehaus.org/browse/MJAVADOC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-244: - Affects Version/s: 2.6 > Javadoc plugin: java files under src/main/javadoc and doc-files dire

[jira] Updated: (MJAVADOC-245) Aggregate does not work

[ http://jira.codehaus.org/browse/MJAVADOC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-245: - Attachment: MJAVADOC-245.zip Are you sure? running mvn site works on mvn 2.0.x and 2.1 and fi

[jira] Updated: (MJAVADOC-246) ExceptionInInitializerError

[ http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-246: - Affects Version/s: 2.6 > ExceptionInInitializerError > --- > >

[jira] Updated: (MJAVADOC-246) ExceptionInInitializerError

[ http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-246: - Priority: Blocker (was: Major) Fix Version/s: 2.6.1 confirmed > ExceptionInInitial

[jira] Commented: (MJAVADOC-249) javadoc:fix should wrap existing comments in

[ http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185719#action_185719 ] jieryn commented on MJAVADOC-249: - Yep, I like that it collapses the {...@inheritdoc} down to one l

[jira] Closed: (MJAVADOC-248) Site 'Usage' page references 2.5 version of m-javadoc-p

[ http://jira.codehaus.org/browse/MJAVADOC-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-248. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.6.1 fixed in [r800

[jira] Updated: (MJAVADOC-249) javadoc:fix should wrap existing comments in

[ http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-249: - Priority: Minor (was: Major) > javadoc:fix should wrap existing comments in > -

[jira] Commented: (MJAVADOC-249) javadoc:fix should wrap existing comments in

[ http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185717#action_185717 ] Vincent Siveton commented on MJAVADOC-249: -- Why do you want to add them by default in your

[jira] Commented: (MJAVADOC-250) javadoc:fix mojo should fully qualify {...@link} class names

[ http://jira.codehaus.org/browse/MJAVADOC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185718#action_185718 ] jieryn commented on MJAVADOC-250: - Does the m-javadoc-p have any class-level sense? By this I mean,

[jira] Closed: (MRELEASE-468) Branch mojo page lists branchName parameter as optional itparameter although it is required

[ http://jira.codehaus.org/browse/MRELEASE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic closed MRELEASE-468. - Resolution: Duplicate Duplicate of MRELEASE-327 > Branch mojo page lists branchName parameter as opt

[jira] Commented: (MJAVADOC-250) javadoc:fix mojo should fully qualify {...@link} class names

[ http://jira.codehaus.org/browse/MJAVADOC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185711#action_185711 ] Vincent Siveton commented on MJAVADOC-250: -- I already thought about this feature but it se

[jira] Created: (SCM-488) Git provider fails to support 'release:perform' if not releasing from remote HEAD

Git provider fails to support 'release:perform' if not releasing from remote HEAD - Key: SCM-488 URL: http://jira.codehaus.org/browse/SCM-488 Project: Maven SCM

[jira] Created: (MRELEASE-468) Branch mojo page lists branchName parameter as optional itparameter although it is required

Branch mojo page lists branchName parameter as optional itparameter although it is required --- Key: MRELEASE-468 URL: http://jira.codehaus.org/browse/MRELEASE-468

[jira] Closed: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor

[ http://jira.codehaus.org/browse/MNG-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3043. -- Resolution: Fixed Revised in [r800294|http://svn.apache.org/viewvc?view=rev&revision=800294]. > Allow

[jira] Created: (MNG-4278) Allow wildcard in server id in settings.xml

Allow wildcard in server id in settings.xml --- Key: MNG-4278 URL: http://jira.codehaus.org/browse/MNG-4278 Project: Maven 2 Issue Type: New Feature Components: Settings Affects Versions:

[jira] Issue Comment Edited: (MRELEASE-400) Failed to validate POM for project ... at ...\release-pom.xml

[ http://jira.codehaus.org/browse/MRELEASE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185677#action_185677 ] Hafga edited comment on MRELEASE-400 at 8/3/09 3:17 AM: I got exact the sam

[jira] Commented: (MRELEASE-400) Failed to validate POM for project ... at ...\release-pom.xml

[ http://jira.codehaus.org/browse/MRELEASE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185677#action_185677 ] Hafga commented on MRELEASE-400: I got exact the same error. Using maven 2.0.8. The POM has an pare