[ http://jira.codehaus.org/browse/MAVEN-1397?page=comments#action_45078 ]
Trygve Laugstol commented on MAVEN-1397:
----------------------------------------
I'm not sure what the best way is, there are at least two solutions to this:
1) The easy way Add setters to the Mojo and use it as a normal bean in jelly.
Then you will have to map the Maven 2 expressions to the Maven 1 ${project}
object etc. This is possible as the MavenProject and ArtifactRepository
actually doesn't seem to be used in the plugin at all. I'll look into removing
those in the morning.
2) The more correct way: Create a infrastructure for embedding Maven 2 and get
Maven to instanciate and execute the Mojo. This will require a way to map a
Maven 1 project to a Maven 2 project and a lot of other stuff.
This is probably way more work than you're ready for and solution 1) will
suffice for now.
> replace test plugin with surefire
> ---------------------------------
>
> Key: MAVEN-1397
> URL: http://jira.codehaus.org/browse/MAVEN-1397
> Project: Maven
> Type: Task
> Reporter: Brett Porter
> Assignee: Emmanuel Venisse
> Priority: Blocker
> Fix For: 1.1-rc1
>
>
> avoid the need for forkmode=once by switching to the superior surefire plugin
> for general testing.
> Enhance the surefire mojo to provide the same output as junit so that the
> test plugin remains backwards compatible.
--
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]
