[
http://jira.codehaus.org/browse/MNG-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MNG-114.
----------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.1)
superceded by local repository proposal
> ability to flip install/plugin repository for development
> ---------------------------------------------------------
>
> Key: MNG-114
> URL: http://jira.codehaus.org/browse/MNG-114
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
> Reporter: Brett Porter
>
> During development, there is the occasional situation where your latest
> change to a component may hose the installation if you are building and
> installing into m2 or the repository m2 uses.
> I think this will particularly affect mojo developers because they are used
> straight from the local repository. John was encountering this while working
> on the compiler.
> This is most likely to bite when the version is the same, which happens when
> it is a SNAPSHOT constantly being developed and tested.
> I suggest a couple of things:
> - the ability to easily run from a different M2_HOME on the command line
> (using the same start script, but flipping homes)
> - this verifies the need to separate the plugin repository from the artifact
> dependency repository
> - I'd like the ability to force the use of a "clean" repository: a read only
> one (where the jars are downloaded but not installed), used at runtime to get
> the plugins while developing via some command line switch when your install
> gets hosed.
> I'm open to further discussion on how this could work, especially in context
> of more light being shed on the plugin repository use itself, and whether
> plugins can be installed for a user by a profile.
--
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
