Remove declarations of third-party repositories from root POM

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.10
  • Fix Version/s: 2.12
  • Component/s: Maven Plugin
  • Labels:
    None

Description

See http://markmail.org/message/iijs5numf2eylvgw

During execution of Sonar analysis by Maven 2.2.1 , it tries to access http://repository.sonarsource.org/content/repositories/sonar/ even if this repository was not declared explicitly by user. And in fact currently this repository is required only to build Sonar, so even if we cannot fully remove it, then we can try to avoid it's usage during analysis.

Also would be cool to enforce during release that third-party repositories not declared.

Issue Links

is related to

Improvement - An improvement or enhancement to an existing feature or task. SONAR-2938 Remove declarations of third-party repositories

  • 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
Freddy Mallet added a comment -

Hi Evgeny, is it still possible to fix this issue as SONAR-1836 has been postponed to Sonar 2.13 ?

Show
Freddy Mallet added a comment - Hi Evgeny, is it still possible to fix this issue as SONAR-1836 has been postponed to Sonar 2.13 ?
Hide
Permalink
Evgeny Mandrikov added a comment -

Hi Freddy,

Into which repository we will deploy new artifacts for PMD and Checkstyle ?
If answer is Codehaus ( using groupId org.codehaus.sonar ), then we definitely can resolve this ticket, since Codehaus synced to Central.
But I suppose that answer would be - into our internal repository. In that case as I said in description : "if we cannot fully remove it, then we can avoid it's usage during analysis". So I can create another ticket for 2.13 about full removal of third-party repositories and this one can be done in 2.12.

Show
Evgeny Mandrikov added a comment - Hi Freddy, Into which repository we will deploy new artifacts for PMD and Checkstyle ? If answer is Codehaus ( using groupId org.codehaus.sonar ), then we definitely can resolve this ticket, since Codehaus synced to Central. But I suppose that answer would be - into our internal repository. In that case as I said in description : "if we cannot fully remove it, then we can avoid it's usage during analysis". So I can create another ticket for 2.13 about full removal of third-party repositories and this one can be done in 2.12.
Hide
Permalink
Evgeny Mandrikov added a comment -

As was discussed today with Freddy and Simon : in version 2.12 declaration should be moved from root pom (in order to remove side effects in Maven plugins) to the place where it's used (i.e. sonar-checkstyle-plugin) and it should be fully removed later when all dependencies would be available in Central (see SONAR-2938).

Show
Evgeny Mandrikov added a comment - As was discussed today with Freddy and Simon : in version 2.12 declaration should be moved from root pom (in order to remove side effects in Maven plugins) to the place where it's used (i.e. sonar-checkstyle-plugin) and it should be fully removed later when all dependencies would be available in Central (see SONAR-2938).
Hide
Permalink
Evgeny Mandrikov added a comment -

Done in eb20690.

Show
Evgeny Mandrikov added a comment - Done in eb20690.
Hide
Permalink
Simon Brandhof added a comment -

Tested

Show
Simon Brandhof added a comment - Tested
Hide
Permalink
Evgeny Mandrikov added a comment -

No need for integration tests.

Show
Evgeny Mandrikov added a comment - No need for integration tests.

People

  • Assignee:
    Evgeny Mandrikov
    Reporter:
    Evgeny Mandrikov
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: