[jira] Reopened: (MNG-3035) Maven caches missing snapshot dependencies, so further builds fail without checking the repo until the cache expires or -U is included to flush the cache

[ http://jira.codehaus.org/browse/MNG-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Parker reopened MNG-3035: - Updated with example and further information (see previous comment) > Maven caches missing snapshot dependencies, so

[jira] Updated: (MNG-3035) Maven caches missing snapshot dependencies, so further builds fail without checking the repo until the cache expires or -U is included to flush the cache

[ http://jira.codehaus.org/browse/MNG-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tom Parker updated MNG-3035: Attachment: MNG-3035.zip See attached pom files and script to build them in the correct order and simulate two dif

[jira] Created: (MNG-3035) Maven caches missing snapshot dependencies, so further builds fail without checking the repo until the cache expires or -U is included to flush the cache

Maven caches missing snapshot dependencies, so further builds fail without checking the repo until the cache expires or -U is included to flush the cache

[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: 2.0-beta-4.patch Description of 2.0-beta-4.patch: Same as PomRewriteVersions.patch but for version 2.0-beta-4. There has been significant refactoring

[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] 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] Commented: (MRELEASE-160) The next snapshot version is not used un submodules

[ http://jira.codehaus.org/browse/MRELEASE-160?page=comments#action_79209 ] Tom Parker commented on MRELEASE-160: - This bug does not effect the dryRun. I believe it was introduced due to testing only in the dryRun situation. dryRun is subtly

[jira] Commented: (MRELEASE-108) NullPointerException when POM has no SCM connection url

[ http://jira.codehaus.org/browse/MRELEASE-108?page=comments#action_79064 ] Tom Parker commented on MRELEASE-108: - this seems to be fixed in the latest snapshot version > NullPointerException when POM has no SCM connection url > -

[jira] Created: (MPSCM-90) p4 command reports most or all errors on stderr but maven-scm-provider-perforce throws away stderr

p4 command reports most or all errors on stderr but maven-scm-provider-perforce throws away stderr -- Key: MPSCM-90 URL: http://jira.codehaus.org/browse/MPSCM-90

[jira] Created: (MRELEASE-172) missing developerConnectionUrl parameter causes missing connectionUrl error message

missing developerConnectionUrl parameter causes missing connectionUrl error message --- Key: MRELEASE-172 URL: http://jira.codehaus.org/browse/MRELEASE-172 Project: Maven