[jira] Commented: (MEAR-42) General setting of dependency filenames

[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_79365 ] Stephane Nicoll commented on MEAR-42: - I am not saying there is no problem, I am saying that using the groupId as part of the file *name* won't fit well. I'll think over

[jira] Updated: (MNGECLIPSE-20) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=all ] Daniel Schulz updated MNGECLIPSE-20: Attachment: mngeclipse20-trigger.jpg problem trigger > using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 > version instead) >

[jira] Commented: (MEAR-42) General setting of dependency filenames

[ http://jira.codehaus.org/browse/MEAR-42?page=comments#action_79363 ] Jonas Olsson commented on MEAR-42: -- It's not the "weirdness" of the filename that's relevant, it's the name collisions. As Maven has introduced groupId to negate artifact col

[jira] Closed: (MNG-2652) Dead links from "Maven Users Centre"

[ http://jira.codehaus.org/browse/MNG-2652?page=all ] Brett Porter closed MNG-2652. - Assignee: Brett Porter Resolution: Fixed applied, thanks! > Dead links from "Maven Users Centre" > > > Key: MNG-2

[jira] Created: (MNG-2652) Dead links from "Maven Users Centre"

Dead links from "Maven Users Centre" Key: MNG-2652 URL: http://jira.codehaus.org/browse/MNG-2652 Project: Maven 2 Issue Type: Bug Components: Documentation: Guides Reporter: Franz Al

[jira] Updated: (MRELEASE-90) Exception if version is SNAPSHOT

[ http://jira.codehaus.org/browse/MRELEASE-90?page=all ] Brett Porter updated MRELEASE-90: - Affects Version/s: 2.0-beta-4 Fix Version/s: (was: 2.0-beta-4) 2.0-beta-5 > Exception if version is SNAPSHOT >

[jira] Updated: (MRELEASE-91) Updating of dependencyManagement inconsistent with updating of dependencies with regard to SNAPSHOTs

[ http://jira.codehaus.org/browse/MRELEASE-91?page=all ] Brett Porter updated MRELEASE-91: - Fix Version/s: (was: 2.0-beta-4) 2.0-beta-5 > Updating of dependencyManagement inconsistent with updating of dependencies > with regard to

[jira] Updated: (MRELEASE-145) release:prepare requires all modules to be SNAPSHOTS

[ http://jira.codehaus.org/browse/MRELEASE-145?page=all ] Brett Porter updated MRELEASE-145: -- Affects Version/s: 2.0-beta-4 Fix Version/s: (was: 2.0-beta-4) > release:prepare requires all modules to be SNAPSHOTS > ---

[jira] Updated: (MRELEASE-115) Issue URL on pom is incorrect

[ http://jira.codehaus.org/browse/MRELEASE-115?page=all ] Brett Porter updated MRELEASE-115: -- Affects Version/s: 2.0-beta-4 Fix Version/s: (was: 2.0-beta-4) > Issue URL on pom is incorrect > - > >

[jira] Updated: (MRELEASE-160) The next snapshot version is not used un submodules

[ http://jira.codehaus.org/browse/MRELEASE-160?page=all ] Tom Parker updated MRELEASE-160: Attachment: PomRewriteVersions.patch Description for PomRewriteVersions.patch. Fix for this issue. I have not tested this patch without first applying dryRun.pa

[jira] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts

[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79360 ] John Tolentino commented on MWAR-58: This got resolved with the fix to MWAR-59. They both use getClassifier() in resolving the default final name. Need some test case thou

[jira] Commented: (MWAR-59) artifact extension set incorrectly in a multi-module build

[ http://jira.codehaus.org/browse/MWAR-59?page=comments#action_79359 ] John Tolentino commented on MWAR-59: Changed code to use getClassifier() instead of getType(). > artifact extension set incorrectly in a multi-module build > -

[jira] Created: (MCHECKSTYLE-61) Upgrade Locator URL logic to use maven-wagon.

Upgrade Locator URL logic to use maven-wagon. - Key: MCHECKSTYLE-61 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-61 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Repo

[jira] Updated: (MRELEASE-160) The next snapshot version is not used un submodules

[ http://jira.codehaus.org/browse/MRELEASE-160?page=all ] Tom Parker updated MRELEASE-160: Attachment: dryRun.patch Fixes behaviour of dryRun. The real thing does this: translate pom.xml to pom.xml in rewrite-poms-for-release phase commit pom.xml transl

[jira] Closed: (MCHECKSTYLE-60) French localisation of the checkstyle report.

[ http://jira.codehaus.org/browse/MCHECKSTYLE-60?page=all ] Joakim Erdfelt closed MCHECKSTYLE-60. - Assignee: Joakim Erdfelt Resolution: Fixed Thanks!. Applied in revision 471615 > French localisation of the checkstyle report. > ---

[jira] Created: (MCHECKSTYLE-60) French localisation of the checkstyle report.

French localisation of the checkstyle report. - Key: MCHECKSTYLE-60 URL: http://jira.codehaus.org/browse/MCHECKSTYLE-60 Project: Maven 2.x Checkstyle Plugin Issue Type: Improvement Affects Vers

[jira] Created: (MECLIPSE-186) In correct head title for the site documentaiton

In correct head title for the site documentaiton Key: MECLIPSE-186 URL: http://jira.codehaus.org/browse/MECLIPSE-186 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Affects Versions: 2.3

[jira] Created: (MEAR-46) Java modules do not work

Java modules do not work Key: MEAR-46 URL: http://jira.codehaus.org/browse/MEAR-46 Project: Maven 2.x Ear Plugin Issue Type: Bug Affects Versions: 2.2, 2.1, 2.0 Reporter: David Blevins Attach

[jira] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts

[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79352 ] John Tolentino commented on MWAR-58: Elliot Metsger: Please use the patch I've attached here in creating your test cases. I've already merged it with MWAR-59 (which is alr

[jira] Updated: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts

[ http://jira.codehaus.org/browse/MWAR-58?page=all ] John Tolentino updated MWAR-58: --- Attachment: MWAR-58-new.patch Merged with current svn code (mostly affected by MWAR-59). > consider the artifact classifier when checking for duplicated artifacts >

[jira] Commented: (MRELEASE-160) The next snapshot version is not used un submodules

[ http://jira.codehaus.org/browse/MRELEASE-160?page=comments#action_79350 ] Joerg Schaible commented on MRELEASE-160: - Hi Tom, I am not talking of the dryRun. The described behavior applies to the real release process. - Jörg > The nex

[jira] Commented: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI

[ http://jira.codehaus.org/browse/MSITE-159?page=comments#action_79349 ] John Allen commented on MSITE-159: -- relative paths were partially supported in beta-4 however the logic did not resolve sibling paths with a common ancestor. Maybe offline

[jira] Closed: (MWAR-59) artifact extension set incorrectly in a multi-module build

[ http://jira.codehaus.org/browse/MWAR-59?page=all ] John Tolentino closed MWAR-59. -- Resolution: Fixed Patch applied--although have to manually insert then test them because they got stale. Thanks for providing tests. > artifact extension set incorrectly

[jira] Created: (MSUREFIRE-178) Known bug should not break the build

Known bug should not break the build Key: MSUREFIRE-178 URL: http://jira.codehaus.org/browse/MSUREFIRE-178 Project: Maven 2.x Surefire Plugin Issue Type: Improvement Components: Junit 3.x suppor

[jira] Commented: (MECLIPSE-132) "Class not found" when run/debug JUnit tests

[ http://jira.codehaus.org/browse/MECLIPSE-132?page=comments#action_79345 ] Przemyslaw Jaskierski commented on MECLIPSE-132: This bug is a killer. When trying to run JUnit test using Eclipse's JUnit launcher I've discovered that n

[jira] Commented: (MSITE-190) Bad file name for external_classic.png in classic skin

[ http://jira.codehaus.org/browse/MSITE-190?page=comments#action_79344 ] J-C Walmetz commented on MSITE-190: --- Issue is with the maven-changes-plugin. My changes.xml file contains the line In the report at the end of the issue, there is a smal

[jira] Commented: (MWAR-58) consider the artifact classifier when checking for duplicated artifacts

[ http://jira.codehaus.org/browse/MWAR-58?page=comments#action_79342 ] John Tolentino commented on MWAR-58: Yes. Please provide test cases if you can. Would greatly demonstrate the use case for the functionality you want added. This is for a

[jira] Updated: (CONTINUUM-978) add web ui tests for all pages related to schedules

[ http://jira.codehaus.org/browse/CONTINUUM-978?page=all ] Marvin King updated CONTINUUM-978: -- Attachment: CONTINUUM978-continuum-webapp-test.patch > add web ui tests for all pages related to schedules > -

[jira] Closed: (MPSCM-63) If project.xml can't be edited (e.g. read only), prepare-release goal still succeeds

[ http://jira.codehaus.org/browse/MPSCM-63?page=all ] Lukas Theussl closed MPSCM-63. -- Assignee: Lukas Theussl Resolution: Fixed Fix Version/s: 1.6.1 > If project.xml can't be edited (e.g. read only), prepare-release goal still > succeeds >

[jira] Commented: (MSITE-190) Bad file name for external_classic.png in classic skin

[ http://jira.codehaus.org/browse/MSITE-190?page=comments#action_79339 ] Dennis Lundberg commented on MSITE-190: --- Which plugin is it that does not work fine because of this, the maven-changes-plugin or the maven-changelog-plugin? What is i

[jira] Closed: (MPSCM-87) CLONE -NPE while performing a scm:prepare-release goal

[ http://jira.codehaus.org/browse/MPSCM-87?page=all ] Lukas Theussl closed MPSCM-87. -- Assignee: Lukas Theussl Resolution: Cannot Reproduce It seems like you are using some outdated version of the plugin, please try with the latest and open another ti

[jira] Commented: (MNG-2486) disallow use of ${project.version} in dependency versions

[ http://jira.codehaus.org/browse/MNG-2486?page=comments#action_79337 ] Olivier Lamy commented on MNG-2486: --- Due to MNG-2651 ? This issue will be fix with 2.0.5 ? > disallow use of ${project.version} in dependency versions > ---