SonarQube Jenkins

Hudson plugin : maven fails if the variable PATH+JDK is defined into Hudson

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1
  • Labels:
    None
  • Number of attachments :
    0

Description

Thanks to Hieu Le Trung for this description on hudson bug tracker :

I have an issue, it's not related to hudson, but sonar plugin.
When I use sonar in my maven2 project, it automatically add the current system
environment variable and there's a variable named PATH+JDK exist when create the
JDK environment.
The PATH+JDK will be put into an XML file and so on it is an invalid XML tag.

I wonder if we can replace that style with other such as "." or "_" or "-"
instead of + since PATH+JDK is an invalid XML tag.

See https://hudson.dev.java.net/issues/show_bug.cgi?id=2615. The problem should come from EnvVars.java.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Roukine added a comment -

Does anyone know how to workaround this issue?

Show
Vincent Roukine added a comment - Does anyone know how to workaround this issue?
Hide
Permalink
Allan Shoup added a comment -

I was able to work around this by installing the Hudson Sonar plugin and using that plugin's configuration instead of specifying the maven goals.

Show
Allan Shoup added a comment - I was able to work around this by installing the Hudson Sonar plugin and using that plugin's configuration instead of specifying the maven goals.
Hide
Permalink
Evgeny Mandrikov added a comment -

Seems like variable name "PATH+JDK" valid only for Windows, I think that you shouldn't use such name and change variable name to be a more portable. So, also I think that this issue can be marked as "won't fix".

Show
Evgeny Mandrikov added a comment - Seems like variable name "PATH+JDK" valid only for Windows, I think that you shouldn't use such name and change variable name to be a more portable. So, also I think that this issue can be marked as "won't fix".
Hide
Permalink
Vincent Roukine added a comment -

I agree that if it was my choice, there won't be a '+' in the variable names. The problem is that we may not always control what variable exists or not on the particular environment that will run the plugin. And ideally, Sonar should be portable to any system with a JRE.

Show
Vincent Roukine added a comment - I agree that if it was my choice, there won't be a '+' in the variable names. The problem is that we may not always control what variable exists or not on the particular environment that will run the plugin. And ideally, Sonar should be portable to any system with a JRE.
Hide
Permalink
Cédric Munger added a comment -

In sonar 1.7 we where adding system properties to the sonar-pom.xml porperties node which was causing this issue. This is not done anymore since 1.8 so the xml produced is now valid

Show
Cédric Munger added a comment - In sonar 1.7 we where adding system properties to the sonar-pom.xml porperties node which was causing this issue. This is not done anymore since 1.8 so the xml produced is now valid

People

  • Assignee:
    Cédric Munger
    Reporter:
    Simon Brandhof
Vote (4)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: