[
http://jira.codehaus.org/browse/MNG-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated MNG-1692:
------------------------------
Fix Version/s: (was: 2.1)
2.x
would need to be framed as a proposal
> Project scoped Repository
> -------------------------
>
> Key: MNG-1692
> URL: http://jira.codehaus.org/browse/MNG-1692
> Project: Maven 2
> Issue Type: Wish
> Components: Artifacts and Repositories
> Reporter: Mark Proctor
> Fix For: 2.x
>
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
