Must the next parent SNAP exist for a downstream artifact release:perform to work ?

[James Levinson <ja...@opower.com>]

A little difficult to explain, but here goes:

We branch from trunk and then release our parent and core together
from SNAPs on our branches. For example,

    <parent>
        <groupId>com.blifnok</groupId>
        <artifactId>main-parent</artifactId>
        <version>3.23.0-SNAPSHOT</version>
    </parent>
    <groupId>com.blifnok</groupId>
    <artifactId>core</artifactId>
    <packaging>jar</packaging>
    <version>3.23.0-SNAPSHOT</version>

I cut the 3.23.0 release of main-parent, but the subsequent perform on
core fails with

Caused by: org.apache.maven.project.ProjectBuildingException: Cannot
find parent: com.blifnok:main-parent for project:
com.blifnok:core:jar:3.23.1-SNAPSHOT for project
com.blifnok:core:jar:3.23.1-SNAPSHOT

The perform appears to be looking for the next development version,
instead of just building the 3.23.0 version of the artifact. Here are
the release.properties created by the prepare:

#release configuration
#Fri Apr 20 14:10:11 PDT 2012
dependency.com.blifnok\:main-parent.release=3.23.0
scm.tagNameFormat=@{project.artifactId}-@{project.version}
scm.tag=3.23.0
dependency.com.blifnok\:main-parent.development=3.23.1-SNAPSHOT
pushChanges=true
scm.url=scm\:svn\:file\:///opt/svnroot/main/core/branches/3.23.x
preparationGoals=clean verify
project.dev.com.blifnok\:core=3.23.1-SNAPSHOT
remoteTagging=true
scm.commentPrefix=[maven-release-plugin]
project.scm.com.blifnok\:core.tag=HEAD
project.rel.com.blifnok\:core=3.23.0
exec.additionalArguments=-DskipTests\=true -P nexus
exec.snapshotReleasePluginAllowed=false
project.scm.com.blifnok\:core.developerConnection=scm\:svn\:file\:///opt/svnroot/main/core/branches/3.23.x
completedPhase=end-release

Obviously, I can just build this SNAPSHOT, but why is the perform
trying to resolve the next parent development version? Is the phase
using "dependency.com.blifnok\:main-parent.development=3.23.1-SNAPSHOT"
instead of "dependency.com.blifnok\:main-parent.release=3.23.0" ? Or,
is it reading this from the pom that was changed by the prepare?
Perhaps, there is a convention or best practice I am unaware of OR
maybe a bug ?

Thanks

--

James Levinson

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org