Hey, thanks! The NPE is gone now, however, this just detaches the parent version…
BUT, I found out about the “versions:update-parent” goal. This works when the new parent version was already deployed
or installed locally.
Kai, not sure if this was already obvious to you, but the californium.* release build jobs will need the following build
step:
Goals: versions:update-parent
Properties: parentVersion=${RELEASE_VERSION}
…
Goals: versions:update-parent scm:checkin
Properties: parentVersion=${NEXT_VERSION}
includes=**/pom.xml
message="Prepare ${NEXT_VERSION}"
One step closer :D
Ciao
Matthias
From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mikael Barbero
Sent: Dienstag, 20. Oktober 2015 15:59
To: Californium (Cf) developer discussions
Subject: Re: [cf-dev] Release new milestone
Try to use version 2.1, 2.2 has a know issue that cause the NPE.
I have been looking into the versions:set issue and it seams to be a general problem with the plugin:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli) on project tools: Project version is inherited from
parent. -> [Help 1]
(longer thread with similar problem: different repos)
A way to get it work is giving the module paths in the parent (californium -> ../californium.*) and call versions:set there. However, then all repos
have to be checked out in a build and we have to disable building the modules when installing the parent.
When setting the version in the top-level modules (californium.*), the plugin has a NPE:
[ERROR] Failed to execute goal org.codehaus.mojo:versions-maven-plugin:2.2:set (default-cli) on project tools: Execution default-cli of goal org.codehaus.mojo:versions-maven-plugin:2.2:set
failed. NullPointerException -> [Help 1]
Not sure how to proceed here.. custom script? Anyone experience with other plugins that might work?
_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev
