[jira] (MRELEASE-730) release:prepare cannot find dependent artefact
[
https://jira.codehaus.org/browse/MRELEASE-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=291936#comment-291936
]
Marius Dumitru Florea commented on MRELEASE-730:
I had a similar problem while using Maven 3.0.3. Upgrading to 3.0.4 fixed the
problem for me.
> release:prepare cannot find dependent artefact
> --
>
> Key: MRELEASE-730
> URL: https://jira.codehaus.org/browse/MRELEASE-730
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.2.2
>Reporter: Thomas Diesler
>
> It seems that release:prepare assumes dependencies to come from central
> {code}
> [tdiesler@tdvaio jbosgi-resolver]$ mvn release:prepare
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] JBossOSGi Resolver
> [INFO] JBossOSGi Resolver API
> [INFO] JBossOSGi Resolver Felix
> [INFO]
>
> [INFO]
>
> [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-release-plugin:2.2.2:prepare (default-cli) @
> jbosgi-resolver-parent ---
> [INFO] Verifying that there are no local modifications...
> [INFO] ignoring changes on: pom.xml.next, release.properties,
> pom.xml.releaseBackup, pom.xml.backup, pom.xml.branch, pom.xml.tag
> [INFO] Executing: /bin/sh -c cd /home/tdiesler/git/jbosgi-resolver && git
> status
> [INFO] Working directory: /home/tdiesler/git/jbosgi-resolver
> [INFO] Checking dependencies and plugins for snapshots ...
> What is the release version for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver API"?
> (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.0.Alpha5: :
> What is the release version for "JBossOSGi Resolver Felix"?
> (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.0.Alpha5: :
> What is SCM release tag or label for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent)
> jbosgi-resolver-parent-2.0.0.Alpha5: :
> What is the new development version for "JBossOSGi Resolver"?
> (org.jboss.osgi.resolver:jbosgi-resolver-parent) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver API"?
> (org.jboss.osgi.resolver:jbosgi-resolver-apiv2) 2.0.1.Alpha5-SNAPSHOT: :
> What is the new development version for "JBossOSGi Resolver Felix"?
> (org.jboss.osgi.resolver:jbosgi-resolver-felix) 2.0.1.Alpha5-SNAPSHOT: :
> [INFO] Transforming 'JBossOSGi Resolver'...
> [INFO] Transforming 'JBossOSGi Resolver API'...
> [INFO] Transforming 'JBossOSGi Resolver Felix'...
> [INFO] Ignoring artifact version update for expression ${project.version}
> [INFO] Not generating release POMs
> [INFO] Executing goals 'clean verify'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has
> been configured for this MavenInvoker instance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO]
>
> [INFO] [INFO] Reactor Build Order:
> [INFO] [INFO]
> [INFO] [INFO] JBossOSGi Resolver
> [INFO] [INFO] JBossOSGi Resolver API
> [INFO] [INFO] JBossOSGi Resolver Felix
> [INFO] [INFO]
>
> [INFO] [INFO]
>
> [INFO] [INFO] Building JBossOSGi Resolver 2.0.0.Alpha5
> [INFO] [INFO]
>
> [INFO] [INFO]
> [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @
> jbosgi-resolver-parent ---
> [INFO] [INFO] Deleting /home/tdiesler/git/jbosgi-resolver/target
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @
> jbosgi-resolver-parent >>>
> [INFO] [INFO]
> [INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @
> jbosgi-resolver-parent <<<
> [INFO] [INFO]
> [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @
> jbosgi-resolver-parent ---
> [INFO] [INFO]
>
> [INFO] [INFO]
>
> [INFO] [INFO] Building JBossOSGi Resolver API 2.0.0.Alpha5
> [INFO] [INFO]
>
> [INFO] Downloading:
> http://repo1.maven.org/maven2/org/jboss/osgi/vfs/jbosgi-vfs30/1.0.6/jbosgi-vfs30-1.0.
[jira] Created: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
release:prepare can fail during rewrite-poms-for-development phase if a
property matches the version being released
---
Key: MRELEASE-666
URL: http://jira.codehaus.org/browse/MRELEASE-666
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.1
Environment: Linux
Reporter: Marius Dumitru Florea
Attachments: maven-release-prepare-debug-log.txt
Executing
{noformat}
mvn release:prepare -DautoVersionSubmodules=true -Pci
{noformat}
against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
order to create
http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
fails with the attached log (I attached only the final part of the console
log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
release version is {{3.0-test-3}}. In other words release:prepare fails if the
version being released matches the {{commons.version}} property defined in the
parent pom. Note that after release:prepare fails all poms are ready to be
committed, i.e. I just had to commit them to finish the release:prepare , so it
looks like release:prepare manages to rewrite the poms for next development
iteration but fails just before committing them for some obscure reason.
I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
[
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259587#action_259587
]
Marius Dumitru Florea commented on MRELEASE-666:
An important detail is that release:prepare succeeds with {{3.0-milestone-3}}
if I use {{-DdryRun=true}} and maven 2.2.1. With maven 3.0.3 it fails both when
run for real and on simulation mode.
> release:prepare can fail during rewrite-poms-for-development phase if a
> property matches the version being released
> ---
>
> Key: MRELEASE-666
> URL: http://jira.codehaus.org/browse/MRELEASE-666
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.1
> Environment: Linux
>Reporter: Marius Dumitru Florea
> Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
> order to create
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
> fails with the attached log (I attached only the final part of the console
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
> release version is {{3.0-test-3}}. In other words release:prepare fails if
> the version being released matches the {{commons.version}} property defined
> in the parent pom. Note that after release:prepare fails all poms are ready
> to be committed, i.e. I just had to commit them to finish the release:prepare
> , so it looks like release:prepare manages to rewrite the poms for next
> development iteration but fails just before committing them for some obscure
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
[
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259643#action_259643
]
Marius Dumitru Florea commented on MRELEASE-666:
{quote}
Note that after release:prepare fails all poms are ready to be committed, i.e.
I just had to commit them to finish the release:prepare, so it looks like
release:prepare manages to rewrite the poms for next development iteration but
fails just before committing them for some obscure reason.
{quote}
Actually I was wrong about this. Most of the POMs were updated but there were a
few that still had {{3.0-milestone-3}} as parent version. So release:prepare
failed in the middle of the rewrite-poms-for-development phase.
> release:prepare can fail during rewrite-poms-for-development phase if a
> property matches the version being released
> ---
>
> Key: MRELEASE-666
> URL: http://jira.codehaus.org/browse/MRELEASE-666
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.1
> Environment: Linux
>Reporter: Marius Dumitru Florea
> Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
> order to create
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
> fails with the attached log (I attached only the final part of the console
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
> release version is {{3.0-test-3}}. In other words release:prepare fails if
> the version being released matches the {{commons.version}} property defined
> in the parent pom. Note that after release:prepare fails all poms are ready
> to be committed, i.e. I just had to commit them to finish the release:prepare
> , so it looks like release:prepare manages to rewrite the poms for next
> development iteration but fails just before committing them for some obscure
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-666) release:prepare can fail during rewrite-poms-for-development phase if a property matches the version being released
[
http://jira.codehaus.org/browse/MRELEASE-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marius Dumitru Florea closed MRELEASE-666.
--
Resolution: Not A Bug
This issue was caused by a mistake in one of our poms: we were using
${commons.version} instead of ${project.version} for an internal dependency
(i.e. a jar that was generated by one of the child modules). Sorry for the
noise.
> release:prepare can fail during rewrite-poms-for-development phase if a
> property matches the version being released
> ---
>
> Key: MRELEASE-666
> URL: http://jira.codehaus.org/browse/MRELEASE-666
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.1
> Environment: Linux
>Reporter: Marius Dumitru Florea
> Attachments: maven-release-prepare-debug-log.txt
>
>
> Executing
> {noformat}
> mvn release:prepare -DautoVersionSubmodules=true -Pci
> {noformat}
> against http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/ @r35313 in
> order to create
> http://svn.xwiki.org/svnroot/xwiki/platform/core/tags/xwiki-core-3.0-milestone-3/
> fails with the attached log (I attached only the final part of the console
> log) when using {{3.0-milestone-3}} as release version. Prepare succeeds if
> release version is {{3.0-test-3}}. In other words release:prepare fails if
> the version being released matches the {{commons.version}} property defined
> in the parent pom. Note that after release:prepare fails all poms are ready
> to be committed, i.e. I just had to commit them to finish the release:prepare
> , so it looks like release:prepare manages to rewrite the poms for next
> development iteration but fails just before committing them for some obscure
> reason.
> I was able to reproduce this with both maven 2.2.1 and 3.0.3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-782) Properties defined in a child pom hide all the properties defined in the parent pom while performing release:prepare
Marius Dumitru Florea created MRELEASE-782:
--
Summary: Properties defined in a child pom hide all the properties
defined in the parent pom while performing release:prepare
Key: MRELEASE-782
URL: https://jira.codehaus.org/browse/MRELEASE-782
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.3.2
Environment: Any
Reporter: Marius Dumitru Florea
Suppose you have this two poms:
{code:title=Parent POM}
...
1.6
...
{code}
{code:title=Child POM}
...
...
...
...
${my.version}
...
{code}
Running release:prepare on this works just fine. Now, if we add a
{{properties}} section with any property to the child pom we get:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
project XYZ: The version could not be updated: ${my.version} -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
project XYZ: The version could not be updated: ${my.version}
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoFailureException: The version could not
be updated: ${commons.version}
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:299)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:247)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.shared.release.ReleaseFailureException: The version
could not be updated: ${my.version}
at
org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.rewriteArtifactVersions(AbstractRewritePomsPhase.java:578)
at
org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:298)
at
org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:220)
at
org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:126)
at
org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.simulate(AbstractRewritePomsPhase.java:713)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:228)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:169)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:146)
at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:107)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:291)
... 22 more
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
[jira] (MRELEASE-782) Properties defined in a child pom hide all the properties defined in the parent pom while performing release:prepare
[
https://jira.codehaus.org/browse/MRELEASE-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=304219#comment-304219
]
Marius Dumitru Florea commented on MRELEASE-782:
You can reproduce this issue with https://github.com/xwiki/xwiki-commons by
adding a {{properties}} section with any property to
https://github.com/xwiki/xwiki-commons/blob/master/xwiki-commons-pom/pom.xml
and running release:perform from repo root.
> Properties defined in a child pom hide all the properties defined in the
> parent pom while performing release:prepare
>
>
> Key: MRELEASE-782
> URL: https://jira.codehaus.org/browse/MRELEASE-782
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.3.2
> Environment: Any
>Reporter: Marius Dumitru Florea
>
> Suppose you have this two poms:
> {code:title=Parent POM}
> ...
>
> 1.6
>
> ...
> {code}
> {code:title=Child POM}
> ...
>
> ...
>
> ...
>
>
> ...
> ${my.version}
>
>
>
> ...
> {code}
> Running release:prepare on this works just fine. Now, if we add a
> {{properties}} section with any property to the child pom we get:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
> project XYZ: The version could not be updated: ${my.version} -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare
> (default-cli) on project XYZ: The version could not be updated: ${my.version}
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.MojoFailureException: The version could
> not be updated: ${commons.version}
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:299)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:247)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: org.apache.maven.shared.release.ReleaseFailureException: The
> version could not be updated: ${my.version}
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.rewriteArtifactVersions(AbstractRewritePomsPhase.java:578)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformDocument(AbstractRewritePomsPhase.java:298)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transformProject(AbstractRewritePomsPhase.java:220)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.transform(AbstractRewritePomsPhase.java:126)
> at
> org.apache.maven.shared.release.phase.AbstractRewritePomsPhase.simulate(AbstractRewritePomsPhase.java:713)
> at
> org.apache.ma
