maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joost den Boer (JIRA)" <>
Subject [jira] Commented: (MSITE-222) -D command line options not recognised
Date Thu, 04 Feb 2010 11:58:55 GMT


Joost den Boer commented on MSITE-222:

I run into the same problem when trying to use a Bamboo buildkey in a link in site.xml. I
want to define this globally and not for each project.

The maven goal I use for testing is: 'mvn clean site -DbambooBuildKey=PROJ-MAIN'. When running
on Bamboo I can change this to 'mvn clean site -DbambooBuildKey=${bamboo.buildKey}' to dynamically
have the Bamboo buildkey available in the project.

When I use ${bambooBuildKey} in a link href in the site.xml, the link contains '${bambooBuildKey}'
and not the substituted value. 
If I define a property in the pom <projectBuildKey>${bambooBuildKey}</projectBuildKey>
this value is correct when running maven; projectBuildKey=PROJ-MAIN.
When using ${projectBuildKey} in the site.xml, the result contains '${bambooBuildKey}' so
'projectBuildKey' value is substituted but not for the correct value.

> -D command line options not recognised
> --------------------------------------
>                 Key: MSITE-222
>                 URL:
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-5
>         Environment: Windows XP, Java 1.5_06
>            Reporter: Carl Husselbee
> It appears as if passing command line args to maven are not being ignored by the site
> I am passing arguments: 
> mvn -P weblogic -DbootstrapProperty=/ package
> and the package is getting the bootstrapProperty property correctly, but when the site
target is executed the
> property is unset.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message