[ http://jira.codehaus.org/browse/MNG-59?page=all ]
Brett Porter updated MNG-59:
----------------------------
Priority: Minor (was: Critical)
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.
was:
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.
Fix Version: (was: 2.0-beta-1)
2.0-beta-2
Environment:
type: Wish (was: New Feature)
> write an m1 component
> ---------------------
>
> Key: MNG-59
> URL: http://jira.codehaus.org/browse/MNG-59
> Project: Maven 2
> Type: Wish
> Reporter: Brett Porter
> Priority: Minor
> Fix For: 2.0-beta-2
>
>
> 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.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
