[jira] (MRELEASE-352) Record Maven version and java version used during release.

[ https://jira.codehaus.org/browse/MRELEASE-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-352. --- Resolution: Won't Fix Assignee: Robert Scholte With MSHARED-38 both the JDK and Maven

[jira] (MRELEASE-787) release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

[ https://jira.codehaus.org/browse/MRELEASE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MRELEASE-787: - release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

[jira] (MINVOKER-115) install goal doesn't install required plugins (from the reactor build) to the local repo

[ https://jira.codehaus.org/browse/MINVOKER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314041#comment-314041 ] Robert Scholte commented on MINVOKER-115: - Since the plugin was created in

[jira] (MINVOKER-115) install goal doesn't install required plugins from the reactor build to the local repo

[ https://jira.codehaus.org/browse/MINVOKER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314107#comment-314107 ] Robert Scholte commented on MINVOKER-115: - Installing all reactor-projects was my first

[jira] (MINVOKER-115) install goal doesn't install required plugins from the reactor build to the local repo

[ https://jira.codehaus.org/browse/MINVOKER-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MINVOKER-115. --- Resolution: Fixed Fix Version/s: 1.8 Assignee: Robert Scholte Fixed in

[jira] (MINVOKER-146) Support modifying maven executable

Robert Scholte created MINVOKER-146: --- Summary: Support modifying maven executable Key: MINVOKER-146 URL: https://jira.codehaus.org/browse/MINVOKER-146 Project: Maven 2.x Invoker Plugin

[jira] (MINVOKER-146) Support modifying maven executable

[ https://jira.codehaus.org/browse/MINVOKER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MINVOKER-146. --- Resolution: Fixed Assignee: Robert Scholte Fixed in

[jira] (MINVOKER-146) Support modifying maven executable

[ https://jira.codehaus.org/browse/MINVOKER-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MINVOKER-146: Affects Version/s: 1.7 Fix Version/s: 1.8 Support modifying maven executable

[jira] (MSHADE-135) Add PluginTransformer

Robert Scholte created MSHADE-135: - Summary: Add PluginTransformer Key: MSHADE-135 URL: https://jira.codehaus.org/browse/MSHADE-135 Project: Maven 2.x Shade Plugin Issue Type: New Feature

[jira] (MRELEASE-803) Inner profile properties for artifact versions block release

Robert Scholte created MRELEASE-803: --- Summary: Inner profile properties for artifact versions block release Key: MRELEASE-803 URL: https://jira.codehaus.org/browse/MRELEASE-803 Project: Maven 2.x

[jira] (MDEP-390) org.apache.maven.plugins:maven-dependency-plugin:get to support unpack

[ https://jira.codehaus.org/browse/MDEP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEP-390. --- Resolution: Duplicate Assignee: Robert Scholte

[jira] (MDEP-390) org.apache.maven.plugins:maven-dependency-plugin:get to support unpack

[ https://jira.codehaus.org/browse/MDEP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MDEP-390: - I'll reopen this issue and adjust the title. Looks like a new feature, see [Issues for

[jira] (MDEP-390) org.apache.maven.plugins:maven-dependency-plugin:unpack to support remoteRepositories

[ https://jira.codehaus.org/browse/MDEP-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MDEP-390: Component/s: (was: get) unpack Assignee: (was: Robert Scholte)

[jira] (MRELEASE-787) release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

[ https://jira.codehaus.org/browse/MRELEASE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314322#comment-314322 ] Robert Scholte commented on MRELEASE-787: - Erik, {quote} [ERROR] svn:

[jira] (MSHADE-135) Add PluginTransformer

[ https://jira.codehaus.org/browse/MSHADE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MSHADE-135: - Assignee: Robert Scholte Add PluginTransformer -

[jira] (MSHADE-135) Add PluginXmlTransformer

[ https://jira.codehaus.org/browse/MSHADE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSHADE-135: -- Summary: Add PluginXmlTransformer (was: Add PluginTransformer) Add PluginXmlTransformer

[jira] (MSHADE-135) Add PluginXmlTransformer

[ https://jira.codehaus.org/browse/MSHADE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MSHADE-135. - Resolution: Fixed Fix Version/s: 3.0 Fixed in [r1413392|https://svn.apache.org/r1413392]

[jira] (MNG-5381) Restore MavenSession.getRepositoryCache()

[ https://jira.codehaus.org/browse/MNG-5381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=314356#comment-314356 ] Robert Scholte commented on MNG-5381: - Fixed in

[jira] (MRELEASE-805) CLONE - scm:cvs dosn't take global .cvsignore from user home dir

Robert Scholte created MRELEASE-805: --- Summary: CLONE - scm:cvs dosn't take global .cvsignore from user home dir Key: MRELEASE-805 URL: https://jira.codehaus.org/browse/MRELEASE-805 Project: Maven

[jira] (SCM-701) CLONE - scm:cvs dosn't take global .cvsignore from user home dir

[ https://jira.codehaus.org/browse/SCM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MRELEASE-805 to SCM-701: - Complexity: Intermediate Component/s: (was:

[jira] (SCM-701) scm:cvs dosn't take global .cvsignore from user home dir

[ https://jira.codehaus.org/browse/SCM-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated SCM-701: --- Summary: scm:cvs dosn't take global .cvsignore from user home dir (was: CLONE - scm:cvs dosn't take global

[jira] (MRELEASE-787) release:prepare-with-pom fails when suppressCommitBeforeTag is used (SVN)

[ https://jira.codehaus.org/browse/MRELEASE-787?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-787. --- Resolution: Fixed I found the cause and fixed it in

[jira] (MNG-5398) scriptSourceDirectory in superpom is not prefixed with ${project.basedir}/

Robert Scholte created MNG-5398: --- Summary: scriptSourceDirectory in superpom is not prefixed with ${project.basedir}/ Key: MNG-5398 URL: https://jira.codehaus.org/browse/MNG-5398 Project: Maven 2 3

[jira] (MNG-5399) Upgrade version of maven-release-plugin in superpom

Robert Scholte created MNG-5399: --- Summary: Upgrade version of maven-release-plugin in superpom Key: MNG-5399 URL: https://jira.codehaus.org/browse/MNG-5399 Project: Maven 2 3 Issue Type:

[jira] (MNG-5399) Upgrade version of maven-release-plugin in superpom to 2.3.2

[ https://jira.codehaus.org/browse/MNG-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MNG-5399: Summary: Upgrade version of maven-release-plugin in superpom to 2.3.2 (was: Upgrade version of

[jira] (MNG-5399) Upgrade version of maven-release-plugin in superpom to 2.3.2

[ https://jira.codehaus.org/browse/MNG-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5399. --- Resolution: Fixed Fix Version/s: 3.1.0 Assignee: Robert Scholte Fixed in

[jira] (MNG-5400) Upgrade version of maven-dependency-plugin in superpom to 2.5

Robert Scholte created MNG-5400: --- Summary: Upgrade version of maven-dependency-plugin in superpom to 2.5 Key: MNG-5400 URL: https://jira.codehaus.org/browse/MNG-5400 Project: Maven 2 3 Issue

[jira] (MNG-5398) scriptSourceDirectory in superpom is not prefixed with ${project.basedir}/

[ https://jira.codehaus.org/browse/MNG-5398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5398. --- Resolution: Fixed Fix Version/s: 3.1.0 Assignee: Robert Scholte Fixed in

[jira] (MNG-5400) Upgrade version of maven-dependency-plugin in superpom to 2.5

[ https://jira.codehaus.org/browse/MNG-5400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5400. --- Resolution: Fixed Fix Version/s: 3.1.0 Assignee: Robert Scholte Fixed in

[jira] (MCOMPILER-189) Source Xref report is missing classes due to simple name collission, update maven-jxr-plugin

Robert Scholte created MCOMPILER-189: Summary: Source Xref report is missing classes due to simple name collission, update maven-jxr-plugin Key: MCOMPILER-189 URL:

[jira] (MRELEASE-592) Please allow de-activation of profiles

[ https://jira.codehaus.org/browse/MRELEASE-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-592. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in

[jira] (MRELEASE-667) Profiles activated in settings.xml can't be deactivated for release

[ https://jira.codehaus.org/browse/MRELEASE-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-667. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed with

[jira] (MRELEASE-614) releaseProfiles works only if at least one (default) profile is activated in the same pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-614: Description: related to MRELEASE-459 I decided to define an empty dummy profile, which is

[jira] (MRELEASE-614) releaseProfiles works only if at least one (default) profile is activated in the same pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-614. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Should be fixed

[jira] (MRELEASE-746) SCM URL being mangled

[ https://jira.codehaus.org/browse/MRELEASE-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-746: Description: When performing {{mvn release:prepare}}, the plugin is removing colons from my

[jira] (MRELEASE-808) prepare-with-pom needs to be run twice when finalName contains ${project.version}

[ https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315077#comment-315077 ] Robert Scholte commented on MRELEASE-808: - I've added a test in

[jira] (SCM-705) Git pushes tag ambigiously

[ https://jira.codehaus.org/browse/SCM-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MRELEASE-807 to SCM-705: - Complexity: Intermediate Component/s: (was: Git)

[jira] (MRELEASE-735) Profile activation working unpredictably

[ https://jira.codehaus.org/browse/MRELEASE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315080#comment-315080 ] Robert Scholte commented on MRELEASE-735: - Could you try the maven-release-plugin

[jira] (MRELEASE-410) Allow specifying specific profiles to execute in the prepare mojo

[ https://jira.codehaus.org/browse/MRELEASE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315081#comment-315081 ] Robert Scholte commented on MRELEASE-410: - I consider to close this as won't fix, because

[jira] (SCM-706) prepare-with-pom deletes release-pom.xml then tries to git add it (presumably so the next commit records the fact)

[ https://jira.codehaus.org/browse/SCM-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MRELEASE-809 to SCM-706: - Complexity: Intermediate Component/s: (was: Git)

[jira] (MRELEASE-729) release:branch makes pom changes for branch in 'master' before branching

[ https://jira.codehaus.org/browse/MRELEASE-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-729. --- Resolution: Duplicate Assignee: Robert Scholte release:branch makes pom changes for

[jira] (MRELEASE-808) Can't generate release-pom.xml when custom finalName contains ${project.version}

[ https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-808: Summary: Can't generate release-pom.xml when custom finalName contains ${project.version}

[jira] (MRELEASE-808) Can't generate release-pom.xml when custom finalName contains ${project.version}

[ https://jira.codehaus.org/browse/MRELEASE-808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-808. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in

[jira] (MRELEASE-553) Allow for preparationProfiles in 'prepare' goal (as releaseProfiles in 'perform' goal)

[ https://jira.codehaus.org/browse/MRELEASE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-553. --- Resolution: Won't Fix Assignee: Robert Scholte Profiles resolution has been improved

[jira] (MRELEASE-418) release plugin not honoring -Darguments passed

[ https://jira.codehaus.org/browse/MRELEASE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-418. --- Resolution: Cannot Reproduce Assignee: Robert Scholte release plugin not honoring

[jira] (MRELEASE-705) Project directory appended twice

[ https://jira.codehaus.org/browse/MRELEASE-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-705. --- Resolution: Incomplete I see no reply on Marks question, so I'll close this as incomplete,

[jira] (MRELEASE-238) release:prepare hangs at cvs update

[ https://jira.codehaus.org/browse/MRELEASE-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-238. --- Resolution: Incomplete If it is still an issue, it's more likely to be an SCM-issue rather than

[jira] (MRELEASE-753) Upgrade to JUnit 4.x

[ https://jira.codehaus.org/browse/MRELEASE-753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-753: Fix Version/s: (was: 2.4) 2.5 Partly done, still need to rewrite the

[jira] (MSCMPUB-7) Add timestamp when commit starts (and ends)

Robert Scholte created MSCMPUB-7: Summary: Add timestamp when commit starts (and ends) Key: MSCMPUB-7 URL: https://jira.codehaus.org/browse/MSCMPUB-7 Project: maven-scm-publish-plugin Issue

[jira] (MDOCCK-28) unknown protocol: scm

[ https://jira.codehaus.org/browse/MDOCCK-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDOCCK-28. Resolution: Not A Bug Assignee: Robert Scholte

[jira] (MRELEASE-811) When I try to specify a pom by a different name for release, the release only looks for pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315719#comment-315719 ] Robert Scholte commented on MRELEASE-811: - Sounds like MRELEASE-618, but that's already

[jira] (MRELEASE-811) When I try to specify a pom by a different name for release, the release only looks for pom.xml

[ https://jira.codehaus.org/browse/MRELEASE-811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-811. --- Resolution: Not A Bug Assignee: Robert Scholte

[jira] (MRELEASE-780) Prevent Tag from additional commits

[ https://jira.codehaus.org/browse/MRELEASE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-780: Component/s: (was: scm) branch Prevent Tag from additional commits

[jira] (MDEPLOY-157) Add deployAtEnd option for multimodule projects

Robert Scholte created MDEPLOY-157: -- Summary: Add deployAtEnd option for multimodule projects Key: MDEPLOY-157 URL: https://jira.codehaus.org/browse/MDEPLOY-157 Project: Maven 2.x and 3.x Deploy

[jira] (MDEPLOY-157) Add deployAtEnd option for multimodule projects

[ https://jira.codehaus.org/browse/MDEPLOY-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MDEPLOY-157: -- Assignee: Robert Scholte Add deployAtEnd option for multimodule projects

[jira] (MDEPLOY-157) Add deployAtEnd option for multimodule projects

[ https://jira.codehaus.org/browse/MDEPLOY-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEPLOY-157. -- Resolution: Fixed Fix Version/s: 2.8 Fixed in

[jira] (MRELEASE-664) [maven release plugin] release:perform wait until build completes before uploading artifacts

[ https://jira.codehaus.org/browse/MRELEASE-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-664. --- Resolution: Won't Fix Assignee: Robert Scholte Solution has been added to the

[jira] (MINSTALL-93) Add installAtEnd option for multimodule projects

Robert Scholte created MINSTALL-93: -- Summary: Add installAtEnd option for multimodule projects Key: MINSTALL-93 URL: https://jira.codehaus.org/browse/MINSTALL-93 Project: Maven 2.x Install Plugin

[jira] (MINSTALL-93) Add installAtEnd option for multimodule projects

[ https://jira.codehaus.org/browse/MINSTALL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MINSTALL-93: -- Assignee: Robert Scholte Add installAtEnd option for multimodule projects

[jira] (MINSTALL-93) Add installAtEnd option for multimodule projects

[ https://jira.codehaus.org/browse/MINSTALL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MINSTALL-93. -- Resolution: Fixed Fix Version/s: 2.5 Fixed in

[jira] (MDEPLOY-143) deploy-file goal insists on deploying javadoc file for previous deploy-file execution

[ https://jira.codehaus.org/browse/MDEPLOY-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MDEPLOY-143: --- Description: I have a pom which I use to package some third party jars to deploy to a local

[jira] (MDEPLOY-150) deploy-file does not use repository url in the same way as deploy

[ https://jira.codehaus.org/browse/MDEPLOY-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MDEPLOY-150: --- Description: We use an own lifecycle here which creates a zip file instead of a jar file. So we

[jira] (MDEPLOY-135) Add ability to skip deploying certain modules from command line

[ https://jira.codehaus.org/browse/MDEPLOY-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEPLOY-135. -- Resolution: Won't Fix Assignee: Robert Scholte Although I can't think of a usecase to only

[jira] (MDEPLOY-97) the buildNumber always be 1 on maven-metadata.xml

[ https://jira.codehaus.org/browse/MDEPLOY-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEPLOY-97. - Resolution: Incomplete Assignee: Robert Scholte No feedback, so closing it as 'incomplete'

[jira] (MDEPLOY-114) Add an option to not fail when remote file already exists and redeploy is forbidden

[ https://jira.codehaus.org/browse/MDEPLOY-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEPLOY-114. -- Resolution: Won't Fix Assignee: Robert Scholte I can think of 2 reasons why a

[jira] (MDEPLOY-143) deploy-file goal insists on deploying javadoc file for previous deploy-file execution

[ https://jira.codehaus.org/browse/MDEPLOY-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315791#comment-315791 ] Robert Scholte commented on MDEPLOY-143: {quote}Uploading:

[jira] (MDEPLOY-143) deploy-file goal insists on deploying javadoc file for previous deploy-file execution

[ https://jira.codehaus.org/browse/MDEPLOY-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315791#comment-315791 ] Robert Scholte edited comment on MDEPLOY-143 at 12/16/12 1:45 PM: --

[jira] (MDEPLOY-120) Unable to deploy large file into Nexus 1.5.0 from Windows Server 2003 Enterprise

[ https://jira.codehaus.org/browse/MDEPLOY-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315792#comment-315792 ] Robert Scholte commented on MDEPLOY-120: Maybe WAGON-381? Unable to

[jira] (MDEPLOY-47) Timeout during SCP upload

[ https://jira.codehaus.org/browse/MDEPLOY-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MDEPLOY-47. - Resolution: Cannot Reproduce Assignee: Robert Scholte No feedback for over a year, so closing

[jira] (MDEPLOY-99) deploy:deploy-file over rights maven-metadata.xml

[ https://jira.codehaus.org/browse/MDEPLOY-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MDEPLOY-99: -- Description: Using {{deploy:deploy-file}} to add multiple version of an artifact causes the

[jira] (MCOMPILER-193) Trying to compile code using maven 3.0.4 version but getting error - illegal character

[ https://jira.codehaus.org/browse/MCOMPILER-193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315959#comment-315959 ] Robert Scholte commented on MCOMPILER-193: -- Have you checked the

[jira] (MRELEASE-798) Commit additional files with release plugin

[ https://jira.codehaus.org/browse/MRELEASE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=315966#comment-315966 ] Robert Scholte commented on MRELEASE-798: - What do you mean with generated/modified? Do

[jira] (MRELEASE-265) Make pom writable on prepare

[ https://jira.codehaus.org/browse/MRELEASE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-265. --- Resolution: Won't Fix Assignee: Robert Scholte {{pom.xml}} shouldn't be read-only in the

[jira] (MRELEASE-398) release:prepare: endlessly asking for the next development version on a multi-module project when not entering the expected value

[ https://jira.codehaus.org/browse/MRELEASE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-398. --- Resolution: Cannot Reproduce Fix Version/s: (was: 2.5) Assignee: Robert

[jira] (MRELEASE-812) perform does not commit tags, deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316051#comment-316051 ] Robert Scholte commented on MRELEASE-812: - {quote}perform does not commit tags, deploys

[jira] (MRELEASE-798) Commit additional files with release plugin

[ https://jira.codehaus.org/browse/MRELEASE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316102#comment-316102 ] Robert Scholte commented on MRELEASE-798: - Ok, so it's related to MRELEASE-51, but I

[jira] (MRELEASE-813) Ability to specify tag for release:perform

[ https://jira.codehaus.org/browse/MRELEASE-813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316146#comment-316146 ] Robert Scholte commented on MRELEASE-813: - Although I'm unfamiliar with Hg and starting

[jira] (SUREFIRE-941) TESTS header printed twice when forkMode is always

Robert Scholte created SUREFIRE-941: --- Summary: TESTS header printed twice when forkMode is always Key: SUREFIRE-941 URL: https://jira.codehaus.org/browse/SUREFIRE-941 Project: Maven Surefire

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-814: Description: If {{developerConnection}} is setup like this in a parent and inherited:

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316401#comment-316401 ] Robert Scholte commented on MRELEASE-814: - Off topic answers: {quote}Maven itself seems

[jira] (MSITE-672) Interpolation of site deploy URL not done in child

[ https://jira.codehaus.org/browse/MSITE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSITE-672: - Description: I have my parent distribution site config filled out like so:

[jira] (DOXIASITETOOLS-77) No content available at http://maven.apache.org/xsd/decoration-1.3.0.xsd

[ https://jira.codehaus.org/browse/DOXIASITETOOLS-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed DOXIASITETOOLS-77. Resolution: Fixed Assignee: Robert Scholte See

[jira] (MRELEASE-816) Various issues with scmCommentPrefix value

[ https://jira.codehaus.org/browse/MRELEASE-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-816. --- Resolution: Won't Fix Assignee: Robert Scholte You're referring to 2 issues: one is a

[jira] (MRELEASE-812) perform does not commit tags, deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316051#comment-316051 ] Robert Scholte edited comment on MRELEASE-812 at 1/3/13 3:42 AM: -

[jira] (MRELEASE-812) prepare does not commit before tagging and therefore deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-812: Summary: prepare does not commit before tagging and therefore deploys snapshot instead of

[jira] (MRELEASE-812) prepare does not commit before tagging and therefore deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316542#comment-316542 ] Robert Scholte commented on MRELEASE-812: - Based on the logs I see the following

[jira] (MRELEASE-812) prepare does not commit before tagging and therefore deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316544#comment-316544 ] Robert Scholte commented on MRELEASE-812: - It has probably to do with SCM-686, so I'm

[jira] (MRELEASE-812) prepare does not commit before tagging and therefore deploys snapshot instead of release

[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-812: Priority: Critical (was: Major) prepare does not commit before tagging and therefore

[jira] (SCM-709) REGRESSION: git status regexps invalid

Robert Scholte created SCM-709: -- Summary: REGRESSION: git status regexps invalid Key: SCM-709 URL: https://jira.codehaus.org/browse/SCM-709 Project: Maven SCM Issue Type: Bug

[jira] (SCM-709) REGRESSION: git status regexps invalid

[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316545#comment-316545 ] Robert Scholte commented on SCM-709: Reference:

[jira] (SCM-709) REGRESSION: git status regexps invalid

[ https://jira.codehaus.org/browse/SCM-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316781#comment-316781 ] Robert Scholte commented on SCM-709: from http://markmail.org/message/trozsqiym4zruj2u {quote} My

[jira] (MRELEASE-595) release:prepare using old SVN structure when creating tag

[ https://jira.codehaus.org/browse/MRELEASE-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316782#comment-316782 ] Robert Scholte commented on MRELEASE-595: - I cannot imagine that this is still an issue.

[jira] (MRELEASE-818) release:perform ignores localCheckout=true

[ https://jira.codehaus.org/browse/MRELEASE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MRELEASE-818: --- Assignee: Robert Scholte release:perform ignores localCheckout=true

[jira] (MSITE-663) Build fails with message Unable to read local module-POM

[ https://jira.codehaus.org/browse/MSITE-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MSITE-663: - Description: Copied from

[jira] (MRELEASE-818) release:perform ignores localCheckout=true

[ https://jira.codehaus.org/browse/MRELEASE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-818. --- Resolution: Fixed Fix Version/s: 2.4.1 Fixed in

[jira] (MRELEASE-704) Perform doesn't use developerConnection from the scm tag

[ https://jira.codehaus.org/browse/MRELEASE-704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-704. --- Resolution: Cannot Reproduce Assignee: Robert Scholte Perform doesn't use

[jira] (SCM-710) Use of encrypted password in pom.xml confiuration is ignored

[ https://jira.codehaus.org/browse/SCM-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317126#comment-317126 ] Robert Scholte commented on SCM-710: Have you followed the instructions of

[jira] (MRELEASE-814) Property interpolation of developerConnection broken when inheritting from parent

[ https://jira.codehaus.org/browse/MRELEASE-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317130#comment-317130 ] Robert Scholte commented on MRELEASE-814: - I've been thinking about this for a couple of

[jira] (SCM-710) Use of encrypted password in pom.xml confiuration is ignored

[ https://jira.codehaus.org/browse/SCM-710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317160#comment-317160 ] Robert Scholte commented on SCM-710: It should be documented somewhere, but I can't find it. Since

[jira] (MRELEASE-819) preparationGoals parameter supoorted before version 2.4

[ https://jira.codehaus.org/browse/MRELEASE-819?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=317193#comment-317193 ] Robert Scholte commented on MRELEASE-819: - It's worse: it seems like all parameters which

<    1   2   3   4   5   6   7   8   9   10   >