If the parent has been released, use the released parent.
It looks like your project "myproject" is getting ${project.version}
from the parent and trying to build a release with SNAPSHOT dependencies
which is not possible.
You should be using the released parent.
<parent>
<artifactId>subco</artifactId>
<groupId>org.mainco.subco</groupId>
<version>52.0.0</version>
</parent>
The fact that the parent does not list the child module is not a factor
in the problem that you are having. It is caused by mixing SNAPSHOTS and
RELEASES in this way.
Ron
On 18/11/2013 4:44 PM, laredotornado-3 wrote:
Hi,
I'm using Maven 3.0.3 and trying to use the Maven release plugin to do a
release of a child module, which inherits from a parent pom. The parent has
been released but does not include the child in its module list, and won't
be able to in the short term. Is it possible to do a release of the child
module? Right now, I'm getting the errors …
mvn -B -DdevelopmentVersion=52.0.0-SNAPSHOT -DreleaseVersion=52.0.0
-Dusername=laredotornado -Dtag=myproject-52.0.0 -DskipTests -P prod
-Dresume=false -DdryRun=true release:prepare
...
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on
project myproject: Can't release project due to non released dependencies :
[ERROR] org.mainco.subco:core:jar:52.0.0-SNAPSHOT:compile
[ERROR] org.mainco.subco:core:test-jar:tests:52.0.0-SNAPSHOT:test
[ERROR] org.mainco.subco:database:jar:52.0.0-SNAPSHOT:compile
[ERROR] org.mainco.subco:pd:jar:52.0.0-SNAPSHOT:compile
[ERROR] org.mainco.subco:session:jar:52.0.0-SNAPSHOT:compile
[ERROR] org.mainco.subco:subco:pom:52.0.0-SNAPSHOT
[ERROR] in project 'myproject'
(org.mainco.subco:myproject:war:52.0.0-SNAPSHOT)
[ERROR] -> [Help 1]
In my pom.xml file, I have the dependencies listed as such:
<parent>
<artifactId>subco</artifactId>
<groupId>org.mainco.subco</groupId>
<version>52.0.0-SNAPSHOT</version>
</parent>
...
<dependency>
<groupId>org.mainco.subco</groupId>
<artifactId>core</artifactId>
<version>${project.version}</version>
</dependency>
I tried adding the dependencies to my pom.xml's dependencyManagement section
(and thus removed the <version> tag from above), but still got the same
error.
--
View this message in context:
http://maven.40175.n5.nabble.com/Is-it-possible-to-release-a-child-module-that-isn-t-listed-in-the-parent-s-list-of-modules-tp5775784.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
