Mailing-List: contact m2-dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven 2 Developers List" <m2-dev@maven.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <3764232.1106819959862.JavaMail.orion@beaver.codehaus.org>
Date: Thu, 27 Jan 2005 04:59:19 -0500 (EST)
From: jira@codehaus.org
To: m2-dev@maven.apache.org
Subject: [jira] Created: (MNG-114) ability to flip install/plugin repository
 for development
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-114

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-114
    Summary: ability to flip install/plugin repository for development
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Brett Porter

    Created: Thu, 27 Jan 2005 4:57 AM
    Updated: Thu, 27 Jan 2005 4:57 AM

Description:
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.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira