You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/27 05:27:06 UTC

[jira] Commented: (MNG-1692) Project scoped Repository

    [ http://jira.codehaus.org/browse/MNG-1692?page=comments#action_52111 ] 

Brett Porter commented on MNG-1692:
-----------------------------------

I don't know if this is the right solution to the problem. It could be useful, however if the workspace functionality is able to identify where the project output files are even without running the build mojos (which would be ideal), then the local repo becomes unnecessary as everything is sourced from the workspace.

However, if that becomes a longer term feature, this could be a quicker fix, and would also assist with interim plugin development.

> Project scoped Repository
> -------------------------
>
>          Key: MNG-1692
>          URL: http://jira.codehaus.org/browse/MNG-1692
>      Project: Maven 2
>         Type: Wish
>   Components: Artifacts and Repositories
>     Reporter: Mark Proctor
>      Fix For: 2.1

>
>
> 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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org