[jira] [Updated] (MRELEASE-709) Release plugin does not work with central repository and always performs clone operation
[
https://issues.apache.org/jira/browse/MRELEASE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-709:
Description:
Plugin cannot work with repositories as if they were central ones. It pushes
and updates data from central repo.
Please take a look at the patch here: SCM-631
Also look at MRELEASE-707 issue. The patch from attachment enables usage of
$\{project.scm.developerConnection} var.
The attached patch makes plugin to work with repository as if it was central.
The following arguments were used for manual testing:
{noformat}
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../ release:prepare
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../ release:perform
{noformat}
was:
Plugin cannot work with repositories as if they were central ones. It pushes
and updates data from central repo.
Please take a look at the patch here: http://jira.codehaus.org/browse/SCM-631
Also look at http://jira.codehaus.org/browse/MRELEASE-707 issue. The patch from
attachment enables usage of ${project.scm.developerConnection} var.
The attached patch makes plugin to work with repository as if it was central.
The following arguments were used for manual testing:
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../ release:prepare
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../ release:perform
Release plugin does not work with central repository and always performs
clone operation
Key: MRELEASE-709
URL: https://issues.apache.org/jira/browse/MRELEASE-709
Project: Maven Release Plugin
Issue Type: Improvement
Components: perform, prepare, scm
Affects Versions: 2.2.1
Environment: Ubuntu 11.04/ArchLinux
Maven 3.0.3
Mercurial 1.7.5/1.9.1
vars:
MAVEN_OPTS=-DaltDeploymentRepository=abetaev::default::file://$HOME/mvn
Reporter: Alexander Betaev
Attachments: maven-release-plugin.patch, maven-release-plugin.patch,
maven-scm.patch, maven-test-project.tar.bz2
Plugin cannot work with repositories as if they were central ones. It pushes
and updates data from central repo.
Please take a look at the patch here: SCM-631
Also look at MRELEASE-707 issue. The patch from attachment enables usage of
$\{project.scm.developerConnection} var.
The attached patch makes plugin to work with repository as if it was central.
The following arguments were used for manual testing:
{noformat}
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../
release:prepare
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../
release:perform
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRELEASE-709) Release plugin does not work with central repository and always performs clone operation
[
https://issues.apache.org/jira/browse/MRELEASE-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481456#comment-14481456
]
Robert Scholte commented on MRELEASE-709:
-
If I understand correctly, this is a HG specific issue. In that case this
should be fixed in the SCM project (maven-scm-patch?). However, that requires a
unittest as well, especially since I'm not familiar with HG.
Release plugin does not work with central repository and always performs
clone operation
Key: MRELEASE-709
URL: https://issues.apache.org/jira/browse/MRELEASE-709
Project: Maven Release Plugin
Issue Type: Improvement
Components: perform, prepare, scm
Affects Versions: 2.2.1
Environment: Ubuntu 11.04/ArchLinux
Maven 3.0.3
Mercurial 1.7.5/1.9.1
vars:
MAVEN_OPTS=-DaltDeploymentRepository=abetaev::default::file://$HOME/mvn
Reporter: Alexander Betaev
Attachments: maven-release-plugin.patch, maven-release-plugin.patch,
maven-scm.patch, maven-test-project.tar.bz2
Plugin cannot work with repositories as if they were central ones. It pushes
and updates data from central repo.
Please take a look at the patch here: SCM-631
Also look at MRELEASE-707 issue. The patch from attachment enables usage of
$\{project.scm.developerConnection} var.
The attached patch makes plugin to work with repository as if it was central.
The following arguments were used for manual testing:
{noformat}
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../
release:prepare
mvn -f parent/pom.xml -DpushChanges=false -DscmPerformLocalUpdate=true
-Dproject.scm.developerConnection=scm:hg:file://\${basedir}/../
release:perform
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MINVOKER-187) Cloned IT project must be writable
[ https://issues.apache.org/jira/browse/MINVOKER-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14480913#comment-14480913 ] Dan Tran edited comment on MINVOKER-187 at 4/6/15 7:21 PM: --- Attach the simple fix to put back the old behavior where clone projects are writable was (Author: dantran): Attach the simple fix and put back the old behavior where clone projects are writable Cloned IT project must be writable -- Key: MINVOKER-187 URL: https://issues.apache.org/jira/browse/MINVOKER-187 Project: Maven Invoker Plugin Issue Type: Bug Affects Versions: 1.10 Reporter: Dan Tran Priority: Critical Attachments: MINVOKER-187.patch m-invoker-p-1.10, it keeps the same file permissions when cloning IT projects to target/it, and fail for not able to interpolate the clone source. This only happens for SCM like Perforce where source by default is read only Here is the stack trace Caused by: java.io.FileNotFoundException: C:\views\dev\maven-tools\plugins\thirdparty-maven-plugin\target\it\cli\pom .xml (Access is denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:213) at java.io.FileOutputStream.init(FileOutputStream.java:162) at org.codehaus.plexus.util.xml.XmlStreamWriter.init(XmlStreamWriter.java:59) at org.codehaus.plexus.util.WriterFactory.newXmlWriter(WriterFactory.java:117) at org.apache.maven.plugin.invoker.AbstractInvokerMojo.buildInterpolatedFile(AbstractInvokerMojo.java:2313) Need this fix in order to upgrade to maven-3.3.x at Perforce environment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT
[
https://issues.apache.org/jira/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-699.
---
Resolution: Won't Fix
Assignee: Robert Scholte
IMHO even the {{release:update-versions}} goal should put the project in a
state ready for the next development cycle. If the {{release:prepare}} doesn't
do its job good enough, we should fix it there. In the meantime you can use the
{{versions-maven-plugin}} which is less strict.
release:update-versions should support -DreleaseVersion too (not only
-DdevelopmentVersion), so it also supports not suffixing the version with
-SNAPSHOT
-
Key: MRELEASE-699
URL: https://issues.apache.org/jira/browse/MRELEASE-699
Project: Maven Release Plugin
Issue Type: Improvement
Components: update-versions
Reporter: Geoffrey De Smet
Assignee: Robert Scholte
Labels: github-pullrequest
Attachments:
0001-MRELEASE-699-release-update-versions-should-support-.patch
The documentation
http://maven.apache.org/plugins/maven-release-plugin/examples/update-versions.html
states The update-versions goal can use the same properties used by the
prepare goal for specifying the versions to be used.
That's not true, as releaseVersion is not supported:
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#releaseVersion
This means, that if you do this:
{{mvn --batch-mode release:update-versions -DdevelopmentVersion=1.2.0}}
that the set version is not 1.2.0, but in fact 1.2.0-SNAPSHOT.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MINVOKER-187) Cloned IT project must be writable
[ https://issues.apache.org/jira/browse/MINVOKER-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated MINVOKER-187: -- Description: m-invoker-p-1.10, it keeps the same file permissions when cloning IT projects to target/it, and fail for not able to interpolate the clone source. This only happens for SCM like Perforce where source by default is read only Here is the stack trace Caused by: java.io.FileNotFoundException: C:\views\dev\maven-tools\plugins\thirdparty-maven-plugin\target\it\cli\pom .xml (Access is denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:213) at java.io.FileOutputStream.init(FileOutputStream.java:162) at org.codehaus.plexus.util.xml.XmlStreamWriter.init(XmlStreamWriter.java:59) at org.codehaus.plexus.util.WriterFactory.newXmlWriter(WriterFactory.java:117) at org.apache.maven.plugin.invoker.AbstractInvokerMojo.buildInterpolatedFile(AbstractInvokerMojo.java:2313) Need this fix in order to upgrade to maven-3.3.x at Perforce environment was: m-invoker-p-1.10, it keeps the same file permissions when cloning IT projects to target/it, and fail for able to interpolate the clone source. This only happens for SCM like Perforce where source by default is read only Here is the stack trace Caused by: java.io.FileNotFoundException: C:\views\dev\maven-tools\plugins\thirdparty-maven-plugin\target\it\cli\pom .xml (Access is denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:213) at java.io.FileOutputStream.init(FileOutputStream.java:162) at org.codehaus.plexus.util.xml.XmlStreamWriter.init(XmlStreamWriter.java:59) at org.codehaus.plexus.util.WriterFactory.newXmlWriter(WriterFactory.java:117) at org.apache.maven.plugin.invoker.AbstractInvokerMojo.buildInterpolatedFile(AbstractInvokerMojo.java:2313) Need this fix in order to upgrade to maven-3.3.x at Perforce environment Cloned IT project must be writable -- Key: MINVOKER-187 URL: https://issues.apache.org/jira/browse/MINVOKER-187 Project: Maven Invoker Plugin Issue Type: Bug Affects Versions: 1.10 Reporter: Dan Tran Priority: Critical Attachments: MINVOKER-187.patch m-invoker-p-1.10, it keeps the same file permissions when cloning IT projects to target/it, and fail for not able to interpolate the clone source. This only happens for SCM like Perforce where source by default is read only Here is the stack trace Caused by: java.io.FileNotFoundException: C:\views\dev\maven-tools\plugins\thirdparty-maven-plugin\target\it\cli\pom .xml (Access is denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.init(FileOutputStream.java:213) at java.io.FileOutputStream.init(FileOutputStream.java:162) at org.codehaus.plexus.util.xml.XmlStreamWriter.init(XmlStreamWriter.java:59) at org.codehaus.plexus.util.WriterFactory.newXmlWriter(WriterFactory.java:117) at org.apache.maven.plugin.invoker.AbstractInvokerMojo.buildInterpolatedFile(AbstractInvokerMojo.java:2313) Need this fix in order to upgrade to maven-3.3.x at Perforce environment -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRELEASE-555) update versions does not update intermodule dependencies
[ https://issues.apache.org/jira/browse/MRELEASE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-555. --- Resolution: Fixed Fixed in [r1671270|http://svn.apache.org/r1671270] update versions does not update intermodule dependencies Key: MRELEASE-555 URL: https://issues.apache.org/jira/browse/MRELEASE-555 Project: Maven Release Plugin Issue Type: Bug Components: update-versions Affects Versions: 2.0 Environment: Maven 2.2.1, JDK 6, XP SP3 Reporter: Michael Osipov Assignee: Robert Scholte Fix For: 2.5.2 Attachments: MRELEASE-555.patch I recently tried the update-versions goal which is really nice and worked well. I cleaned my local repo today and reran mvn package on a multi-module project. It failed due tue a depenceny error. My project was previously on version 2.6.1-SNAPSHOT. Module war depends on module jar with the same version. When doing a release:prepare, the plugin perfectly bumps this intermodule dependency. The release:update-versions missed that dep spot. My build process failed. The goal should crawl for those deps too and update them if autoVersionSubmodules is on. (Same behavior as the prepare goal) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRELEASE-552) Add useEditMode option to release:update-versions
[ https://issues.apache.org/jira/browse/MRELEASE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-552. --- Resolution: Fixed Fix Version/s: 2.5.2 Assignee: Robert Scholte Fixed in [r1671271|http://svn.apache.org/r1671271] Add useEditMode option to release:update-versions - Key: MRELEASE-552 URL: https://issues.apache.org/jira/browse/MRELEASE-552 Project: Maven Release Plugin Issue Type: Improvement Components: update-versions Affects Versions: 2.0 Reporter: Russ Kociuba Assignee: Robert Scholte Priority: Minor Fix For: 2.5.2 Attachments: MRELEASE-552.patch My SCM (TFS) needs to checkout files in order to be able to edit them. Thus the current version of the update-versions goal fails because the files are read-only. The ability to set the useEditMode option to true would fix this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRELEASE-358) CheckDependencySnapshotsPhase fails when resolving all dependencies
[ https://issues.apache.org/jira/browse/MRELEASE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-358. --- Resolution: Incomplete Assignee: Robert Scholte CheckDependencySnapshotsPhase fails when resolving all dependencies --- Key: MRELEASE-358 URL: https://issues.apache.org/jira/browse/MRELEASE-358 Project: Maven Release Plugin Issue Type: Bug Components: prepare Affects Versions: 2.0-beta-7 Reporter: Rich Seller Assignee: Robert Scholte Attachments: patch.txt In CheckDependencySnapshotsPhase, if '0' (All) is selected in response to the prompt specify the selection number ... the dependencies are not removed from the original set, so a ReleaseFailureException is thrown at the end of checkProject(). In the attached patch the dependencies are removed from the original set, and the snapshotSet is returned from resolveSnapshots() to be checked in checkProject(). In the tests, I implemented a custom Prompter because I don't know how to set multiple conditional responses on JMock1 mocks. One other change made while testing: in processSnapshot, What is the next development version? is set with a singleton list so a different value has been entered. I removed the list to make the supplied value the default but allow different responses. I can raise this as a separate issue if required -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MRELEASE-900) release:prepare goal uses parent directory of real repository location
[
https://issues.apache.org/jira/browse/MRELEASE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MRELEASE-900:
Component/s: prepare
release:prepare goal uses parent directory of real repository location
--
Key: MRELEASE-900
URL: https://issues.apache.org/jira/browse/MRELEASE-900
Project: Maven Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.5.1
Reporter: Jens Rabe
Priority: Blocker
I have this in my pom.xml:
{code:xml}
scm
connectionscm:git:http://my-git-server.example.com/git/somebody/my-project.git/connection
developerConnectionssh://g...@my-git-server.example.com:10022/somebody/my-project.git/developerConnection
urlhttp://my-git-server.example.com/git/somebody/my-project/url
/scm
{code}
When I do a mvn release:prepare, it tries to push the tag to
ssh://g...@my-git-server.example.com:10022/somebody/ instead of
ssh://g...@my-git-server.example.com:10022/somebody/my-project.git, causing
the release prepare to fail with Access denied.
When I add a fake file at the end, like:
{code:xml}
scm
connectionscm:git:http://my-git-server.example.com/git/somebody/my-project.git/.git/connection
developerConnectionssh://g...@my-git-server.example.com:10022/somebody/my-project.gi/.gitt/developerConnection
urlhttp://my-git-server.example.com/git/somebody/my-project/url
/scm
{code}
the release:prepare works, but release:perform fails because it is using the
URL as-is.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MRELEASE-906) Upgrade to SCM 1.9.4
[ https://issues.apache.org/jira/browse/MRELEASE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-906. --- Resolution: Fixed Fixed in [r1671508|http://svn.apache.org/r1671508] Upgrade to SCM 1.9.4 Key: MRELEASE-906 URL: https://issues.apache.org/jira/browse/MRELEASE-906 Project: Maven Release Plugin Issue Type: Task Reporter: Robert Scholte Assignee: Robert Scholte Fix For: 2.5.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MEAR-213) WARNING Output is not correct in case of classifiers
[
https://issues.apache.org/jira/browse/MEAR-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MEAR-213:
-
Fix Version/s: (was: 2.10.1)
3.0
WARNING Output is not correct in case of classifiers
Key: MEAR-213
URL: https://issues.apache.org/jira/browse/MEAR-213
Project: Maven Ear Plugin
Issue Type: Improvement
Affects Versions: 2.10
Reporter: Karl Heinz Marbaise
Fix For: 3.0
In relationship with classifier this does not work correctly.
{noformat}
[INFO] --- maven-ear-plugin:2.10:ear (default-ear) @ middletier-ear ---
[WARNING] The artifactId component-base:6.33.10-SNAPSHOT exists more than
once in the modules list.
[WARNING] -- com.company:component-base:jar:6.33.10-SNAPSHOT (jar)
[WARNING] -- com.company:component-base:jar:qclasses:6.33.10-SNAPSHOT (jar)
[WARNING] The artifactId component-func:6.33.10-SNAPSHOT exists more than
once in the modules list.
[WARNING] -- com.company:component-func:jar:6.33.10-SNAPSHOT (jar)
[WARNING] -- com.company:component-func:jar:qclasses:6.33.10-SNAPSHOT (jar)
[WARNING] HINT: This can be simply solved by using the
fileNameMappingfull/fileNameMapping
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MRELEASE-843) Child modules defined in profiles aren't updated by update-versions
[
https://issues.apache.org/jira/browse/MRELEASE-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14481084#comment-14481084
]
Robert Scholte commented on MRELEASE-843:
-
Are we talking about active or inactive profiles?
Child modules defined in profiles aren't updated by update-versions
---
Key: MRELEASE-843
URL: https://issues.apache.org/jira/browse/MRELEASE-843
Project: Maven Release Plugin
Issue Type: Bug
Components: update-versions
Reporter: M. Justin
When I do a mvn:update-versions for a multi-module project that has one of
its modules defined in a profile, the modules defined in the profile don't
have their versions updated. I would expect these modules to also be updated.
{code:title=pom.xml}project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
packagingpom/packaging
groupIdcom.example/groupId
artifactIdexample-parent/artifactId
version1.0.0-SNAPSHOT/version
modules
moduleexample-module1/module
/modules
profiles
profile
idmy-profile/id
modules
moduleexample-module2/module
/modules
/profile
/profiles
scm
developerConnectionscm:git:examplerepo:example.git/developerConnection
/scm
/project
{code}
In this example, when I execute mvn release:update-versions, I get queried to
update example-parent and example-module1, but not example-module2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MRELEASE-857) release:perform does not pass argument -Dsettings.security to inner maven process
[
https://issues.apache.org/jira/browse/MRELEASE-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-857.
---
Resolution: Not A Problem
Assignee: Robert Scholte
Just use {{-Darguments=}} to pass arguments to the {{maven-release-plugin}}
release:perform does not pass argument -Dsettings.security to inner maven
process
---
Key: MRELEASE-857
URL: https://issues.apache.org/jira/browse/MRELEASE-857
Project: Maven Release Plugin
Issue Type: Bug
Components: perform
Reporter: Slawomir Jaranowski
Assignee: Robert Scholte
When we run mvn release:perform with -Dsettings.security=custom-security.xml
first step use our custom security file, but inner process use standard
location of master password file.
This issue are more important after MRELEASE-766, because prepared
settings.xml file more often contains encrypted password.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MRELEASE-738) Provide ability to create new version of release version from release other release version [regular patch scenario]
[ https://issues.apache.org/jira/browse/MRELEASE-738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-738. --- Resolution: Duplicate Assignee: Robert Scholte Provide ability to create new version of release version from release other release version [regular patch scenario] Key: MRELEASE-738 URL: https://issues.apache.org/jira/browse/MRELEASE-738 Project: Maven Release Plugin Issue Type: New Feature Components: update-versions Reporter: Paul Green Assignee: Robert Scholte Currently release version (using maven release plugin) can be created only from snapshot version - which works fine but didn't cover the scenario when you need to patch branch tag and create new version (patched) of release and not doing that from trunk (that contains snapshot version) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRELEASE-860) update-versions goal does not update dependency versions
[
https://issues.apache.org/jira/browse/MRELEASE-860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-860.
---
Resolution: Duplicate
update-versions goal does not update dependency versions
Key: MRELEASE-860
URL: https://issues.apache.org/jira/browse/MRELEASE-860
Project: Maven Release Plugin
Issue Type: Bug
Components: update-versions
Affects Versions: 2.4.2
Reporter: Alex Pogrebnyak
When you run 'prepare-with-pom' goal, it will update snapshot version number
on dependencies.
Contrary to that behavior, update-versions, will only update parent's version.
If you have these poms:
{code:title=aggregator-pom.xml|borderStyle=solid}
artifactIdaggregator/artifactId
parent
groupIdmy.group.id/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
relativePathparent/pom.xml/relativePath
/parent
modules
moduledependent/module
moduledependency/module
/modules
{code}
{code:title=dependent-pom.xml|borderStyle=solid}
artifactIddependent/artifactId
parent
groupIdmy.group.id/groupId
artifactIdparent/artifactId
version1.0-SNAPSHOT/version
relativePath../parent/pom.xml/relativePath
/parent
dependencies
dependency
groupIdmy.group.id/groupId
artifactIddependency/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
{code}
Then, when you run
{code}
mvn -DdevelopmentVersion=1.1-SNAPSHOT -DautoVersionSubmodules=true
release:update-versions
{code}
The dependent-pom.xml will be incorrect:
{code:title=dependent-pom-1.1.xml|borderStyle=solid|xml}
artifactIddependent/artifactId
parent
groupIdmy.group.id/groupId
artifactIdparent/artifactId
version1.1-SNAPSHOT/version
relativePath../parent/pom.xml/relativePath
/parent
dependencies
dependency
groupIdmy.group.id/groupId
artifactIddependency/artifactId
version1.0-SNAPSHOT/version
/dependency
/dependencies
{code}
Notice that dependency's version is still {{{color:red}1.0-SNAPSHOT{color}}}
If I were to do {{release:prepare}} and {{release:perform}} the version would
have been updated in both places to {{1.1-SNAPSHOT}}
I expect the same behavior for {{release:update-versions}} as well.
Just to state: I cannot use $\{project.version\}. And custom version
property does not work because of MRELEASE-782
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MRELEASE-660) Didn't find password for CVSROOT
[
https://issues.apache.org/jira/browse/MRELEASE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-660.
---
Resolution: Not A Problem
Assignee: Robert Scholte
Let's agree that this is not a {{maven-release-plugin}} problem.
Didn't find password for CVSROOT
Key: MRELEASE-660
URL: https://issues.apache.org/jira/browse/MRELEASE-660
Project: Maven Release Plugin
Issue Type: Bug
Affects Versions: 2.0
Environment: Windows Vista, Eclipse 3.6, mvn release:prepare from
shell without tortoise
Reporter: luca preziati
Assignee: Robert Scholte
Attachments: error.TXT
I launch mvn release:prepare and the tool didn't find password for CVSROOT.
I didn't have the file .cvspass.
I can't release a version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MRELEASE-906) Upgrade to SCM 1.9.4
Robert Scholte created MRELEASE-906: --- Summary: Upgrade to SCM 1.9.4 Key: MRELEASE-906 URL: https://issues.apache.org/jira/browse/MRELEASE-906 Project: Maven Release Plugin Issue Type: Task Reporter: Robert Scholte Assignee: Robert Scholte Fix For: 2.5.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
