Sonar

Sonar Maven repository are always in status "In Service - Checking remote ..." when declared in Nexus engine

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.9
  • Component/s: Maven repository
  • Labels:
    None
  • Number of attachments :
    0

Description

When the nexus engine is unable to call the root page of a Maven repository, the status of this repository remains "In Service - Checking remote" in the Nexus console, even if Nexus manages to download artifacts.

In case of Sonar, the root page http://sonarserver:sonarport/deploy/maven always returns "HTTP Error 403".

At least, this page shouldn't return an HTTP error but only a simple text message (like the README.txt page). What would be nice is to allow navigation inside this Sonar Maven Repository (like http://repo1.maven.org/maven2/).

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Simon Brandhof added a comment -

Can not reproduce anymore with nexus 1.3.1. Sonar 1.9 generates also SHA1 and MD5 files in internal repository. It certainly helps to remove error logs.

Show
Simon Brandhof added a comment - Can not reproduce anymore with nexus 1.3.1. Sonar 1.9 generates also SHA1 and MD5 files in internal repository. It certainly helps to remove error logs.
Hide
Permalink
Geert Schuring added a comment -

I just installed Nexus 1.3.3 and Sonar 1.8 and have this exact issue. Is there any solution known?

Show
Geert Schuring added a comment - I just installed Nexus 1.3.3 and Sonar 1.8 and have this exact issue. Is there any solution known?
Hide
Permalink
Olivier Gaudin added a comment -

1.9 seems to fix the issue. It should be out in a couple of days

Show
Olivier Gaudin added a comment - 1.9 seems to fix the issue. It should be out in a couple of days
Hide
Permalink
Josh Devins added a comment -

Reproduced with:
Sonar: 1.9.2
Nexus: 1.2.0.3
Java: 1.6

Workaround for the following versions appears to be simply doing a "touch" on index.html in the deploy/maven directory.

Show
Josh Devins added a comment - Reproduced with: Sonar: 1.9.2 Nexus: 1.2.0.3 Java: 1.6 Workaround for the following versions appears to be simply doing a "touch" on index.html in the deploy/maven directory.
Hide
Permalink
Julien HENRY added a comment -

With Nexus 1.6 and new autoblocking feature my Sonar (1.12) repository was blocked. The workaround about creating an empty index.html in ${SONAR_HOME}/war/sonar-web/deploy/maven seems to works. Could you please add such a file in standard distribution.

Thanks for the tip Josh

Show
Julien HENRY added a comment - With Nexus 1.6 and new autoblocking feature my Sonar (1.12) repository was blocked. The workaround about creating an empty index.html in ${SONAR_HOME}/war/sonar-web/deploy/maven seems to works. Could you please add such a file in standard distribution. Thanks for the tip Josh
Hide
Permalink
Simon Brandhof added a comment -

Thank you guys. The file index.html is added in version 2.1. See SONAR-1520.

Show
Simon Brandhof added a comment - Thank you guys. The file index.html is added in version 2.1. See SONAR-1520.

People

Vote (3)
Watch (2)

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.