Sonar Jenkins

Define a Root POM field

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.1
  • Fix Version/s: 1.2
  • Labels:
    None
  • Environment:
    Hudson V1.306, Sonar 1.9, Sonar Plugin 1.0.1.
  • Number of attachments :
    0

Description

Unable to define a root pom within a subdirectory. The sonar plugin defaults to -f pom.xml but need the ability to override to -f subdir/pom.xml

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. SONAR-706 Sonar doesn't work with a flat maven project

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Evgeny Mandrikov added a comment -

Correct me if I'm wrong:
For maven2 builds Root POM value will be taken from build configuration (section "Build") and there you can specify "subdir/pom.xml".

Show
Evgeny Mandrikov added a comment - Correct me if I'm wrong: For maven2 builds Root POM value will be taken from build configuration (section "Build") and there you can specify "subdir/pom.xml".
Hide
Permalink
Michel Schudel added a comment -

Evgeny,

This indeed applies to maven2 builds, but in in freestyle project, you have no way of setting the pom.xml, it defaults to "pom.xml". So it would be nice to add an input box "pom location/pom file" to the Sonar configuration on project level.

Show
Michel Schudel added a comment - Evgeny, This indeed applies to maven2 builds, but in in freestyle project, you have no way of setting the pom.xml, it defaults to "pom.xml". So it would be nice to add an input box "pom location/pom file" to the Sonar configuration on project level.
Hide
Permalink
Renato Garcia added a comment -

I'm using HUDSON-1.1 plugin and Hudson 1.336 with a maven2 build, and I have this problem too. It used to work on previous hudson versions for me, but I think that hudson has changed the way it handles the build config. It uses the build steps now, so I think the plugin is no longer able to determine the correct pom, and I beleive it uses -f pom.xml by default. So this is no longer working for maven2 builds too. I was wondering if there is a workaround for this?

Tks and regards,
Renato

Show
Renato Garcia added a comment - I'm using HUDSON-1.1 plugin and Hudson 1.336 with a maven2 build, and I have this problem too. It used to work on previous hudson versions for me, but I think that hudson has changed the way it handles the build config. It uses the build steps now, so I think the plugin is no longer able to determine the correct pom, and I beleive it uses -f pom.xml by default. So this is no longer working for maven2 builds too. I was wondering if there is a workaround for this? Tks and regards, Renato
Hide
Permalink
dutoit cédric added a comment -

fix ideas:

  • have an option to define/override basic pom (root pom)
  • detect and allow "-f .*xml" to override -f pom.xml default option
Show
dutoit cédric added a comment - fix ideas: have an option to define/override basic pom (root pom) detect and allow "-f .*xml" to override -f pom.xml default option
Hide
Permalink
Nicolas Dordet added a comment -

Renato,

Since I upgrade to the latest Hudson version (1.337) and sonar-hudson plugin 1.1,
in the build section of hudson, I replace "parentModule/pom.xml" by an empty field (equivalent to "pom.xml").
It seems that now hudson recognize the parent module and go throught it before executing the project's build or the sonar goal. So you have to change your configuration.

Show
Nicolas Dordet added a comment - Renato, Since I upgrade to the latest Hudson version (1.337) and sonar-hudson plugin 1.1, in the build section of hudson, I replace "parentModule/pom.xml" by an empty field (equivalent to "pom.xml"). It seems that now hudson recognize the parent module and go throught it before executing the project's build or the sonar goal. So you have to change your configuration.
Hide
Permalink
Renato Garcia added a comment -

Hi Nicolas,

I made the changes you suggested, along with a change in the svn url, and it worked!

Tks for the advice!!!

Show
Renato Garcia added a comment - Hi Nicolas, I made the changes you suggested, along with a change in the svn url, and it worked! Tks for the advice!!!
Hide
Permalink
Evgeny Mandrikov added a comment -

If I understand correctly, this should be fixed only for non-maven builds?

Show
Evgeny Mandrikov added a comment - If I understand correctly, this should be fixed only for non-maven builds?
Hide
Permalink
Evgeny Mandrikov added a comment - - edited

Now for freestyle project Root POM can be specified. NOTE: If you are using Sonar "Light", then file will be created and existing overwritten.

Show
Evgeny Mandrikov added a comment - - edited Now for freestyle project Root POM can be specified. NOTE: If you are using Sonar "Light", then file will be created and existing overwritten.

People

  • Assignee:
    Evgeny Mandrikov
    Reporter:
    Paul Cox
Vote (5)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved: