[jira] (SCM-188) Add the posibility of adding an entire directory to SCM

[ https://jira.codehaus.org/browse/SCM-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez closed SCM-188. -- Resolution: Incomplete Fix Version/s: (was: future) I'm closing it as it's probably no longer

[jira] (MRELEASE-747) Support Jazz SCM

[ https://jira.codehaus.org/browse/MRELEASE-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed MRELEASE-747. - Resolution: Fixed Assignee: Olivier Lamy fixed r1329108 Thanks! Support

[jira] (SCM-670) Support Jazz SCM

[ https://jira.codehaus.org/browse/SCM-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-670. Resolution: Fixed Fix Version/s: 1.7 Assignee: Olivier Lamy fixed r1329106 Thanks!

[jira] (SCM-154) Bazaar tests should not assume bzr is installed

[ https://jira.codehaus.org/browse/SCM-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-154. Resolution: Fixed Fix Version/s: (was: future) 1.7 Assignee: Olivier Lamy

[jira] (SCM-632) Faulty svn commandline is generated for passwords containing redirection characters

[ https://jira.codehaus.org/browse/SCM-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-632. Resolution: Fixed Fix Version/s: 1.7 Assignee: Olivier Lamy recent p-u version should fix that.

[jira] (SCM-672) Perforce checking (submit) incorrectly ignores working directory

[ https://jira.codehaus.org/browse/SCM-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-672: - Fix Version/s: 1.7 Assignee: Olivier Lamy Perforce checking (submit) incorrectly ignores working

[jira] (SCM-671) Perforce provider Edit command incorrectly ignores working Directory

[ https://jira.codehaus.org/browse/SCM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy updated SCM-671: - Fix Version/s: 1.7 Assignee: Olivier Lamy Perforce provider Edit command incorrectly ignores

[jira] (SCM-672) Perforce checking (submit) incorrectly ignores working directory

[ https://jira.codehaus.org/browse/SCM-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed SCM-672. Resolution: Fixed applied. Thanks! Perforce checking (submit) incorrectly ignores working

[jira] (SCM-671) Perforce provider Edit command incorrectly ignores working Directory

[ https://jira.codehaus.org/browse/SCM-671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297017#comment-297017 ] Olivier Lamy commented on SCM-671: -- applied. Thanks! Perforce provider Edit command

[jira] (ARCHETYPE-406) Support of velocity expressions for user-defined properties

[ https://jira.codehaus.org/browse/ARCHETYPE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297022#comment-297022 ] Alistair A. Israel commented on ARCHETYPE-406: -- Does

[jira] (MDEP-351) dependency:tree is not resolved on assembly project with ear dependency type

Eric TOUTUT created MDEP-351: Summary: dependency:tree is not resolved on assembly project with ear dependency type Key: MDEP-351 URL: https://jira.codehaus.org/browse/MDEP-351 Project: Maven 2.x

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Latombe updated MSITE-604: -- Attachment: MSITE-604-maven3-2.patch Second patch only on site-plugin, still limited to Maven 3

[jira] (MCHANGES-272) Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions.

[ https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297028#comment-297028 ] Benson Margulies commented on MCHANGES-272: --- What about timestamp snapshots? Those

[jira] (MDEP-187) dependency:copy fails when invoked from m2e with workspace resolution enabled

[ https://jira.codehaus.org/browse/MDEP-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolás Cornaglia updated MDEP-187: --- Attachment: MDEP-187c.diff My 2cents to this bug with m2e. Added support to copy the expanded

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297036#comment-297036 ] Vedavyas Panneershelvam commented on MRELEASE-679: -- Using Maven version 3.0.3

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297036#comment-297036 ] Vedavyas Panneershelvam edited comment on MRELEASE-679 at 4/23/12 9:03 AM:

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297036#comment-297036 ] Vedavyas Panneershelvam edited comment on MRELEASE-679 at 4/23/12 9:07 AM:

[jira] (MJAR-153) Missing continuation characters in Export-Package field

Rich Seddon created MJAR-153: Summary: Missing continuation characters in Export-Package field Key: MJAR-153 URL: https://jira.codehaus.org/browse/MJAR-153 Project: Maven 2.x JAR Plugin Issue

[jira] (MNG-5278) deploy:deploy does not work for only Deploying artifact to Maven Remote repo

Himanshu Goyal created MNG-5278: --- Summary: deploy:deploy does not work for only Deploying artifact to Maven Remote repo Key: MNG-5278 URL: https://jira.codehaus.org/browse/MNG-5278 Project: Maven 2 3

[jira] (MJAR-153) Missing continuation characters in Export-Package field

[ https://jira.codehaus.org/browse/MJAR-153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297052#comment-297052 ] Jane Young commented on MJAR-153: - The same problem is happening in Import-Package field.

[jira] (SCM-577) SvnCheckInConsumer is English locale dependent

[ https://jira.codehaus.org/browse/SCM-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SCM-577. -- Resolution: Duplicate Assignee: Robert Scholte SvnCheckInConsumer is English locale dependent

[jira] (MRELEASE-723) DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

[ https://jira.codehaus.org/browse/MRELEASE-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen updated MRELEASE-723: Attachment: add-tag-to-release-poms-1329108.patch Modify patch to work with r1329108.

[jira] (MCHANGES-272) Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions.

[ https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297061#comment-297061 ] Dennis Lundberg commented on MCHANGES-272: -- The need for such an option indicates to me

[jira] (MRELEASE-679) CLONE -release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ https://jira.codehaus.org/browse/MRELEASE-679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297063#comment-297063 ] Robert Scholte commented on MRELEASE-679: - Vedavyas, Does the pom.xml from which you try

[jira] (MCHANGES-272) Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions.

[ https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297064#comment-297064 ] Christian Schulte commented on MCHANGES-272: I would like to be able to enable the

[jira] (MCHANGES-272) Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions.

[ https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=297065#comment-297065 ] Benson Margulies commented on MCHANGES-272: --- I would commit this if I could find the

[jira] (MCHANGES-272) Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions.

[ https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MCHANGES-272: --- Attachment: MCHANGES-272.patch Updated patch to use 'ArtifactUtils.isSnapshot'. I am

[jira] (MCHANGES-272) Please add an option to the 'changes-check' goal to allow skipping release date checks of snapshot versions.

[ https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benson Margulies closed MCHANGES-272. - Resolution: Fixed Fix Version/s: 2.7

[jira] (SCM-670) Support Jazz SCM

[ https://jira.codehaus.org/browse/SCM-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Graham updated SCM-670: - Attachment: jazz-site-xml-update.patch patch to add in the missing site link to the tck tests page generated by

[jira] (SCM-670) Support Jazz SCM

[ https://jira.codehaus.org/browse/SCM-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Graham reopened SCM-670: -- Oops. I forgot to add in the TCK Tests degtails page into site.xml. Patch attached, Support