[jira] Issue Comment Edited: (MSITE-222) -D command line options not recognised

["Joost den Boer (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MSITE-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209128#action_209128 ] 

Joost den Boer edited comment on MSITE-222 at 2/4/10 6:00 AM:
--------------------------------------------------------------

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.

Problem occurs in version 2.0-beta7. Tried version 2.1 but got exception because there are 2 versions of the Log class.
Env: XP with Maven 2.2.0 and Java 1.5.014.

      was (Author: jdboer):
    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: http://jira.codehaus.org/browse/MSITE-222
>             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 plugin.
> I am passing arguments: 
> mvn -P weblogic -DbootstrapProperty=/testbootstrap.properties -Dhelm.target=dev package site
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira