[jira] Created: (MRELEASE-127) default goal in release:perform (should be deploy site site:deploy instead of deploy site:deploy)

default goal in release:perform (should be deploy site site:deploy instead of deploy site:deploy) - Key: MRELEASE-127 URL: http://jira.codehaus.org/browse/MRELEASE-127 Project:

[jira] Created: (MEV-407) Missing POM for spring-support 2.0-m4

Missing POM for spring-support 2.0-m4 - Key: MEV-407 URL: http://jira.codehaus.org/browse/MEV-407 Project: Maven Evangelism Type: Bug Components: Missing POM Reporter: Julien Dubois Attachments: spring-support-2.0-m4.pom

[jira] Updated: (MEV-407) Missing POM for spring-support 2.0-m4

[ http://jira.codehaus.org/browse/MEV-407?page=all ] Julien Dubois updated MEV-407: -- Attachment: spring-support-2.0-m4.pom Missing POM for spring-support 2.0-m4 - Key: MEV-407 URL:

[jira] Created: (MEV-408) Missing POMs for Spring 2.0-m5

Missing POMs for Spring 2.0-m5 -- Key: MEV-408 URL: http://jira.codehaus.org/browse/MEV-408 Project: Maven Evangelism Type: Bug Components: Missing POM Reporter: Julien Dubois As always, the Spring pom.xml files are missing in

[jira] Commented: (MRELEASE-127) default goal in release:perform (should be deploy site site:deploy instead of deploy site:deploy)

[ http://jira.codehaus.org/browse/MRELEASE-127?page=comments#action_66601 ] Grzegorz Slowikowski commented on MRELEASE-127: --- Invoked goals are: deploy site-deploy. site-deploy is the last phase of the site lifecycle (invoking site:deploy). So

[jira] Commented: (MJAR-4) Multiline description provides invalid header in the generated jar files

[ http://jira.codehaus.org/browse/MJAR-4?page=comments#action_66609 ] Filippos Slavik commented on MJAR-4: I can confirm that this very issue is still unresolved. I'm using a clean 2.0.4 maven installation. Multiline description provides invalid

[jira] Created: (MNG-2343) DefaultMaven ignores MavenExecutionRequest.getBaseDirectory() when looking for POM file

DefaultMaven ignores MavenExecutionRequest.getBaseDirectory() when looking for POM file --- Key: MNG-2343 URL: http://jira.codehaus.org/browse/MNG-2343 Project: Maven 2 Type: Bug

[jira] Closed: (MRM-89) add sitemesh to webapp

[ http://jira.codehaus.org/browse/MRM-89?page=all ] Brett Porter closed MRM-89: --- Resolution: Fixed add sitemesh to webapp -- Key: MRM-89 URL: http://jira.codehaus.org/browse/MRM-89 Project: Maven

[jira] Created: (SUREFIRE-44) Inner class inclusion too powerful

Inner class inclusion too powerful -- Key: SUREFIRE-44 URL: http://jira.codehaus.org/browse/SUREFIRE-44 Project: surefire Type: Bug Versions: 2.0 Reporter: Ken Arnold When inner classes were included, it was done in a

[jira] Created: (MPH-14) Add a mojo to print the dependency tree

Add a mojo to print the dependency tree --- Key: MPH-14 URL: http://jira.codehaus.org/browse/MPH-14 Project: Maven 2.x Help Plugin Type: New Feature Reporter: Kenney Westerhof Priority: Minor This mojo should print a

[jira] Commented: (SUREFIRE-44) Inner class inclusion too powerful

[ http://jira.codehaus.org/browse/SUREFIRE-44?page=comments#action_66613 ] Ken Arnold commented on SUREFIRE-44: I thought I had a workaround -- make classes static, etc. But I don't. Because of things like this: public interface

[jira] Commented: (MPH-14) Add a mojo to print the dependency tree

[ http://jira.codehaus.org/browse/MPH-14?page=comments#action_66614 ] Mike Perham commented on MPH-14: Unlike the dependency report tree, I would hope this tree includes version numbers. 90% of the time I need to see the dep tree in order to resolve

[jira] Created: (SUREFIRE-45) Include/Exclude by class name, not file name

Include/Exclude by class name, not file name Key: SUREFIRE-45 URL: http://jira.codehaus.org/browse/SUREFIRE-45 Project: surefire Type: New Feature Reporter: Ken Arnold Right now I include/exclude based on file

[jira] Commented: (MNG-2343) DefaultMaven ignores MavenExecutionRequest.getBaseDirectory() when looking for POM file

[ http://jira.codehaus.org/browse/MNG-2343?page=comments#action_66618 ] Stepan Roh commented on MNG-2343: - Stupid me. It of course is 2.1 and not 2.0.5. Don't know if it applies to 2.0.5 too. DefaultMaven ignores MavenExecutionRequest.getBaseDirectory()

[jira] Created: (WAGONHTTP-10) Use Pragma: no-cache only when appropriate

Use Pragma: no-cache only when appropriate -- Key: WAGONHTTP-10 URL: http://jira.codehaus.org/browse/WAGONHTTP-10 Project: wagon-http Type: Improvement Environment: Maven 2.0.4, Mac OS X 10.4.6 Reporter: Gordon Henriksen

[jira] Commented: (MNG-1181) MavenEmbedder.execute() doesn't run reactor modules

[ http://jira.codehaus.org/browse/MNG-1181?page=comments#action_66620 ] Stepan Roh commented on MNG-1181: - I tried to use maven-embedder from SVN branch maven-2.0.x which claims to hold 2.0.5-SNAPSHOT, but that is not working. Where can I download working

[jira] Commented: (MNGECLIPSE-116) Embedder can't find local repository

[ http://jira.codehaus.org/browse/MNGECLIPSE-116?page=comments#action_66621 ] Wolfgang S commented on MNGECLIPSE-116: --- I have tried v 0.0.8 and v 0.0.9 replacing maven-embedder-2.0.4-dep.jar with the patched version provided here using eclipse

[jira] Commented: (MPIR-28) improve convergence report

[ http://jira.codehaus.org/browse/MPIR-28?page=comments#action_66622 ] Olivier Lamy commented on MPIR-28: -- I think Ready for release must say yes when all snapshots are in the reactors ? -- Olivier improve convergence report --

[jira] Commented: (MNGECLIPSE-116) Embedder can't find local repository

[ http://jira.codehaus.org/browse/MNGECLIPSE-116?page=comments#action_66624 ] Ovidio Mallo commented on MNGECLIPSE-116: - Hi Wolfgang, have you also applied the provided patch? This is necessary since the fixed embedder still (legitimately) throws

[jira] Updated: (MDEPLOY-33) [deploy-file] When deploying a snapshot version with the pomFile specified, POM and artifact get different build numbers

[ http://jira.codehaus.org/browse/MDEPLOY-33?page=all ] John Casey updated MDEPLOY-33: -- Version: 2.2 Fix Version: 2.3 [deploy-file] When deploying a snapshot version with the pomFile specified, POM and artifact get different build numbers

[jira] Closed: (MDEPLOY-33) [deploy-file] When deploying a snapshot version with the pomFile specified, POM and artifact get different build numbers

[ http://jira.codehaus.org/browse/MDEPLOY-33?page=all ] John Casey closed MDEPLOY-33: - Resolution: Fixed had to pass the pomFile (generated or provided) to the artifactDeployer instead of the main project artifact file...this artifact file is passed

[jira] Created: (MPMD-33) do not fail build on PMD failures, include them in pmd report

do not fail build on PMD failures, include them in pmd report - Key: MPMD-33 URL: http://jira.codehaus.org/browse/MPMD-33 Project: Maven 2.x Pmd Plugin Type: Improvement Versions: 2.1 Reporter:

[jira] Commented: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.

[ http://jira.codehaus.org/browse/MJAR-38?page=comments#action_66647 ] Steven Coco commented on MJAR-38: - Including empty tags to squelch the attributes should work out well! Great work. Thanks again. PS: I'm going to file an RFE in the Sun database to

[jira] Updated: (MJAR-38) Maven Puts Arbitrary Extension Definition in JAR Manifest by Default.

[ http://jira.codehaus.org/browse/MJAR-38?page=all ] Jochen Wiedmann updated MJAR-38: Attachment: MJAR-38.patch Maven Puts Arbitrary Extension Definition in JAR Manifest by Default. -

[jira] Updated: (MJAR-7) jar plugin recreates jar files all the time

[ http://jira.codehaus.org/browse/MJAR-7?page=all ] Jochen Wiedmann updated MJAR-7: --- Attachment: plexus-archiver-up2date.patch jar plugin recreates jar files all the time --- Key: MJAR-7 URL:

[jira] Commented: (MRELEASE-119) Release plugin is not updating changes.xml like it did in m1

[ http://jira.codehaus.org/browse/MRELEASE-119?page=comments#action_66657 ] Olivier Lamy commented on MRELEASE-119: --- duplicate with http://jira.codehaus.org/browse/MRELEASE-51 Release plugin is not updating changes.xml like it did in m1

[jira] Created: (MECLIPSE-113) refactored code

refactored code --- Key: MECLIPSE-113 URL: http://jira.codehaus.org/browse/MECLIPSE-113 Project: Maven 2.x Eclipse Plugin Type: Improvement Versions: 2.2 Environment: Windows XP SP2 - Java 1.5.0.6 - Eclipse 3.2M7 Reporter: Francesco Tinti

[jira] Closed: (MRM-116) Execute discoverer and indexing (if no index exists yet) when the repository webapp is accessed.

[ http://jira.codehaus.org/browse/MRM-116?page=all ] Maria Odea Ching closed MRM-116: Resolution: Fixed Created a class (DiscovererExecution) that would be executed when the repository webapp is accessed and no index exists yet. Refactored

[jira] Created: (ARCHETYPE-39) Add tool for working with escaping in Velocity templates

Add tool for working with escaping in Velocity templates Key: ARCHETYPE-39 URL: http://jira.codehaus.org/browse/ARCHETYPE-39 Project: Maven Archetype Type: Improvement Components: Plugin Versions:

[jira] Closed: (MRM-12) POI directory structure incorrectly converted from m1 repo

[ http://jira.codehaus.org/browse/MRM-12?page=all ] Edwin Punzalan closed MRM-12: - Resolution: Fixed Fixed in SVN POI directory structure incorrectly converted from m1 repo -- Key:

[jira] Commented: (MRM-67) Index maintenance

[ http://jira.codehaus.org/browse/MRM-67?page=comments#action_66674 ] Maria Odea Ching commented on MRM-67: - Okay, we'll use the plexus configuration file for the index maintenance. Index maintenance - Key: MRM-67

[jira] Closed: (MDEPLOY-33) [deploy-file] When deploying a snapshot version with the pomFile specified, POM and artifact get different build numbers

[ http://jira.codehaus.org/browse/MDEPLOY-33?page=all ] John Casey closed MDEPLOY-33: - Resolution: Duplicate [deploy-file] When deploying a snapshot version with the pomFile specified, POM and artifact get different build numbers

[jira] Commented: (MDEPLOY-28) Deployment should delete remote files and create new ones instead of modifying them

[ http://jira.codehaus.org/browse/MDEPLOY-28?page=comments#action_66678 ] John Casey commented on MDEPLOY-28: --- I'd like to push this issue off until we can get wagon fixed. I don't believe it should hold up a release based on the other bugfixes in this

[jira] Created: (MAVENUPLOAD-931) Echomine Feridian Version 1.0b2 Maven Uploads

Echomine Feridian Version 1.0b2 Maven Uploads - Key: MAVENUPLOAD-931 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-931 Project: maven-upload-requests Type: Task Reporter: Chris Chen Feridian xmpp module

[jira] Reopened: (MNG-2344) Support for functional/integration tests is *way* too limited

[ http://jira.codehaus.org/browse/MNG-2344?page=all ] Craig McClanahan reopened MNG-2344: --- MNG-591 does not come *close* to covering what actually is needed here. The following are some comments I made on the Struts mailing list, in response to