[MNG-1692] Project scoped Repository

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Incomplete
• Component/s: Artifacts and Repositories
• Assignee: Unassigned
• Reporter: Mark Proctor
• Created: 26/Nov/05 22:08
• Updated: 27/Jun/14 14:32
• Resolved: 19/Jan/14 15:43

Description

In multi module builds I would like jars to not instally locally until I instruct it and still be able to build individual modules. At the moment if I try and build an invidiual module it insists on looking in the local repo. In Maven 1 we worked around this by using jar override.

The use case for this is for when you are messing around with multiple checkouts of the same version and don't want them to interact with each other. With current M2 I either have to create different versions in the pom for each checkout, when all changes are likely to end up in the "master" checkout for a specific verison. Or I can specify the repo to be in the project, but that means I have to checkout everything each time I want to build something.

This could be achieve by using root/target as a project level repo for the produced jars which would use the local repo for anything that it can't find it the project repo. Only when I tell it to install will it copy the jars from the project repo to the local repo.

Issue Links

• is related to: MNG-1694 Build execution order control in fine grained projects.