jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Sonar
  • SONAR-4

Maven plugin conflict with the goal 'site'

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: None
  • Fix Version/s: 1.1
  • Component/s: None
  • Labels:
    None

Description

Request from martin ehrnhoefer on the mailing list :

does anyone know how the Sonar plugin interferes with the Maven build
cycle phases?
E.g. it would be nice to execute the plugin during site creation, but
that doesn't seem to work:

"mvn ch.hortis.sonar:sonar-maven-plugin:1.0.1:sonar site"
...produces a strange build error:
Error occured when triggering measures calculation job on remote
server
Embedded error: Error occured during file http://c1vie021:9000/batch_job/measures_calculations
download
Server returned HTTP response code: 403 for URL:
http://c1vie021:9000/batch_job/measures_calculations

(without "site", the build succeeds)

So, the "solution" for my nightly build is: First run Maven with
targets "install site", then run Maven again with target
"ch.hortis.sonar:sonar-maven-plugin:1.0.1:sonar". Is this the correct
way?

Activity

  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Cédric Munger added a comment - 28/Dec/07 6:33 AM

cannot reproduce this error on 1.1 sonar maven plugin, either the plugin refactoring from 1.0.1 release has solved this issue, either it was an apache web server proxy configuration problem since on 1.0.1 release jetty is never configured to return 403 error codes. It indicates that the http call was probably made trough an apache proxy which returned the 403 http code

Show
Cédric Munger added a comment - 28/Dec/07 6:33 AM cannot reproduce this error on 1.1 sonar maven plugin, either the plugin refactoring from 1.0.1 release has solved this issue, either it was an apache web server proxy configuration problem since on 1.0.1 release jetty is never configured to return 403 error codes. It indicates that the http call was probably made trough an apache proxy which returned the 403 http code

People

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

Dates

  • Created:
    17/Dec/07 6:28 AM
    Updated:
    08/Jan/08 11:25 AM
    Resolved:
    28/Dec/07 6:33 AM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.