Back after a lengthy hiatus.
Any specifics on this profile? How does it get activated? For me, it
does not appear to be activated during release. After searching
around, here is what I have come up with:
In my pom:
<profile>
<id>release-profile</id>
<activation>
<property>
<name>performRelease</name>
<value>true</value>
</property>
</activation>
<build>
<filters>
<filter>src/main/filters/release.properties</
filter>
</filters>
</build>
</profile>
And then on the CL:
mvn -DperformRelease=true release:prepare
The properties in that release.properties file are ignored, and
consequently my plugin fails the build, and thus the release.
So what am I doing wrong?
J
PS. Just for reference (this is the part of the release that fails):
mvn clean integration-test --no-plugin-updates -
Dmaven.buildNumber.skipCheck=true
outputs true as expected for maven.buildNumber.skipCheck, whereas:
mvn clean integration-test --no-plugin-updates -P release-profile
outputs false, when src/main/filters/release.properties looks like:
maven.buildNumber.skipCheck=true
The plugin grabs the value of maven.buildNumber.skipCheck like so:
/**
* If this is made true, we don't check for modified files.
*
* @parameter expression="${maven.buildNumber.skipCheck}"
default-value="false"
*/
private boolean skipCheck;
On 26-Sep-06, at 2:39 PM, Douglas Ferguson wrote:
We have a special profile for releasing that sets some extra
variables.
-----Original Message-----
From: Julian Wood [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 26, 2006 3:00 PM
To: Maven Users List
Subject: Release question
When releasing an artifact, during release:prepare, I get to this
point:
...
[INFO] Executing preparation goals 'clean integration-test'...
[INFO] Executing: mvn clean integration-test --no-plugin-updates -P
deploy-config,deploy-config
[INFO] Scanning for projects...
...
Is there a way to modify the command above:
mvn clean integration-test --no-plugin-updates -P deploy-
config,deploy-config
such that it has additional parameters?
mvn clean integration-test --no-plugin-updates -P deploy-
config,deploy-config -Dmaven.buildNumber.skipCheck=true
or can it automatically inherit said parameters from the original
command?
mvn release:prepare -Dmaven.buildNumber.skipCheck=true
Alternatively, is there a way for my plugin to determine that it is
being executed in the context of a release? I do not want it to
execute certain things at any point during release.
Thanks,
J
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Julian Wood <[EMAIL PROTECTED]>
Software Engineer
Teaching & Learning Centre
University of Calgary
http://tlc.ucalgary.ca
