Maven 2.x and 3.x Site Plugin

-D command line options not recognised

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Incomplete
  • Affects Version/s: 2.0-beta-5
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Environment:
    Windows XP, Java 1.5_06
  • Number of attachments :
    0

Description

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.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Dennis Lundberg added a comment -

What do you want to use the properties for when the site target is being run?

Show
Dennis Lundberg added a comment - What do you want to use the properties for when the site target is being run?
Hide
Permalink
Joost den Boer added a comment - - edited

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.

Show
Joost den Boer added a comment - - edited 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.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.