[jira] Work Stopped: (MNG-59) write an m1 component

[ji...@codehaus.org]

Message:

   Work on this issue has been stopped by Brett Porter (mailto:brett@codehaus.org)

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-59
    Summary: write an m1 component
       Type: New Feature

     Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-2

   Assignee: Brett Porter
   Reporter: Brett Porter

    Created: Mon, 2 Aug 2004 5:34 PM
    Updated: Sun, 19 Sep 2004 10:29 AM

Description:
write a component that runs an m1 instance.

An m1 component could be called upon to run an m1 build whenever it is encountered (v3 POM) or by a compat. flag on the command line. The m1 component just pulls down the m1 POM (eg maven-1.0.pom - not the project's pom), reads the deps (we'd need the v3 reader working 
here), pulls them down using existing m2 stuff, then creates a forehead classloader manually, and fires up a new MavenSession (bypassing the CLI stuff).

I think I'd code that up fairly quickly, and then we have a way to run m1 stuff from m2, but not necessarily integrate it (just give a better way to migrate, and avoids a multiple install dilemma). It may even be possible to mix builds in a reactor by detecting the POM version. 
Some properties could be shared from m2 to override the defaults in m1 so they coexist nicely.




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