[jira] Commented: (MRM-598) Validation error on new repository creation and other fields under certain conditions

[ http://jira.codehaus.org/browse/MRM-598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126641 ] Gunther Walther commented on MRM-598: - Found a probable cause - the validation code checks for 1.000 instead of 1000.

[jira] Commented: (MRM-727) Archiva does not download plugin artifacts

[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126673 ] Maria Odea Ching commented on MRM-727: -- Hi James, I was able to reproduce the plugin download problem in Geronimo. The

[jira] Updated: (MRM-727) Archiva does not download plugin artifacts

[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maria Odea Ching updated MRM-727: - Attachment: MRM-727-build-stack-trace.txt Archiva does not download plugin artifacts

[jira] Commented: (MRM-727) Archiva does not download plugin artifacts

[ http://jira.codehaus.org/browse/MRM-727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126674 ] Maria Odea Ching commented on MRM-727: -- Christian, I think the dom4j problem is a different one. I got those errors from

[jira] Closed: (CONTINUUM-1687) Improve the template and build definition names

[ http://jira.codehaus.org/browse/CONTINUUM-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed CONTINUUM-1687. -- Assignee: Wendy Smoak Resolution: Fixed Fix Version/s: 1.2 Fixed in r635404

[jira] Commented: (MAVENUPLOAD-1932) Update j2ssh-common and j2ssh-core

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126615 ] Carlos Sanchez commented on MAVENUPLOAD-1932: - If you are not using maven as your build system but want

[jira] Closed: (MPLUGIN-82) Fix test for javadoc tools

[ http://jira.codehaus.org/browse/MPLUGIN-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-82. -- Resolution: Fixed Apply Fix test for javadoc tools --

[jira] Commented: (MNG-3395) Default core plugin versions in the superpom.

[ http://jira.codehaus.org/browse/MNG-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126624 ] Paul Benedict commented on MNG-3395: I'd also like to see added: maven-archetype-plugin maven-resources-plugin

[jira] Commented: (MNG-3395) Default core plugin versions in the superpom.

[ http://jira.codehaus.org/browse/MNG-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126627 ] Brian Fox commented on MNG-3395: Resources is in there, or it should be. IMO, archetype is evolving too quickly to lock it

[jira] Commented: (MNG-3395) Default core plugin versions in the superpom.

[ http://jira.codehaus.org/browse/MNG-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126635 ] Paul Benedict commented on MNG-3395: Brian, you were right about resources plugin. I missed it because it wasn't in

[jira] Updated: (MEAR-35) Generate id for modules in application.xml

[ http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Jensen updated MEAR-35: Attachment: ear-module-id.patch The attached patch allows the module ID to be supplied explicitly through a

[jira] Closed: (DOXIA-75) XhtmlSink#figureCaption() writes an alt attribute, but a title attribute would also be appropriate

[ http://jira.codehaus.org/browse/DOXIA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-75. -- Assignee: Lukas Theussl (was: Fabrice BELLINGARD) Resolution: Won't Fix Fix Version/s:

[jira] Commented: (MEV-530) Broken checksum for org/apache/maven/maven/2.0.6/maven-2.0.6.pom

[ http://jira.codehaus.org/browse/MEV-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126655 ] Jonathan Carr commented on MEV-530: --- I'll second that - I'm getting the same warning as Peter. Broken checksum for

[jira] Updated: (MECLIPSE-395) Plugin tests are failing due to a wrong local repository path.

[ http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-395: - Fix Version/s: (was: 2.5) Plugin tests are failing due to a wrong local repository

[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects

[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126656 ] Arnaud Heritier commented on MECLIPSE-344: -- This last issue is reported in MECLIPSE-397 but I'm not surethat it

[jira] Closed: (MECLIPSE-344) connecting existing workspace artifact-projects

[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-344. Resolution: Fixed I think we solved all problems discussed on the mailing list. I close the

[jira] Closed: (SUREFIRE-422) Strip Maven from report title

[ http://jira.codehaus.org/browse/SUREFIRE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed SUREFIRE-422. -- Resolution: Fixed fixed in r635366 thanks Strip Maven from report title

[jira] Updated: (SUREFIRE-422) Strip Maven from report title

[ http://jira.codehaus.org/browse/SUREFIRE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SUREFIRE-422: --- Fix Version/s: (was: 2.x) 2.5 Strip Maven from report title

[jira] Closed: (MECLIPSE-392) Output is written to src/main/webapp instead of target

[ http://jira.codehaus.org/browse/MECLIPSE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-392. Resolution: Fixed Fix Version/s: 2.5 The manifest parameter is now correctly used to

[jira] Created: (ARCHETYPE-147) Cannot create a new project from an exist project

Cannot create a new project from an exist project - Key: ARCHETYPE-147 URL: http://jira.codehaus.org/browse/ARCHETYPE-147 Project: Maven Archetype Issue Type: Bug Components:

[jira] Commented: (ARCHETYPE-147) Cannot create a new project from an exist project

[ http://jira.codehaus.org/browse/ARCHETYPE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126670 ] chenliang commented on ARCHETYPE-147: - The structure of the jar of create-from-project is: META-INF -maven

[jira] Issue Comment Edited: (ARCHETYPE-147) Cannot create a new project from an exist project

[ http://jira.codehaus.org/browse/ARCHETYPE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126670 ] chenliang edited comment on ARCHETYPE-147 at 3/9/08 9:13 PM: - The structure of the jar of

[jira] Issue Comment Edited: (ARCHETYPE-147) Cannot create a new project from an exist project

[ http://jira.codehaus.org/browse/ARCHETYPE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126670 ] chenliang edited comment on ARCHETYPE-147 at 3/9/08 9:28 PM: - The structure of the jar of

[jira] Issue Comment Edited: (MNG-2807) ciManagement from parent is not merging with children

[ http://jira.codehaus.org/browse/MNG-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124607 ] paul4christ79 edited comment on MNG-2807 at 3/9/08 10:00 PM: - This would greatly help when