Maven 2 & 3

Physically separate plugins (and their dependencies) from project artifacts/dependencies in the local repository

Details

  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

This is basically a follow-up to MNG-4191. The separation on the remote side gets partly useless if we continue to store plugins and project artifacts in the same local repository. Once the artifacts have been locally cached by a former build, dependency resolution in another build can no longer detect whether it would have been able to resolve the same artifact remotely by the intended remote repos.

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MNG-4191 separate plugin and artifact 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
Brett Porter added a comment -

this just means the metadata, not the physical artifacts? Otherwise, there'd be quite a lot of duplication.

This was one of the reasons I advocated separating the metadata locations in the local repository: http://docs.codehaus.org/display/MAVEN/Local+Repository+Separation

Show
Brett Porter added a comment - this just means the metadata, not the physical artifacts? Otherwise, there'd be quite a lot of duplication. This was one of the reasons I advocated separating the metadata locations in the local repository: http://docs.codehaus.org/display/MAVEN/Local+Repository+Separation
Hide
Permalink
Conny Kreyssel added a comment -

Will this probably addressed in 3.1?

Show
Conny Kreyssel added a comment - Will this probably addressed in 3.1?

People

  • Assignee:
    Unassigned
    Reporter:
    Benjamin Bentmann
Vote (3)
Watch (2)

Dates

  • Created:
    Updated: