You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2008/12/13 19:53:19 UTC
[jira] Moved: (MANTTASKS-135) Maven Tasks for Ant should provide an
Ant task to launch Maven
[ http://jira.codehaus.org/browse/MANTTASKS-135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann moved MNG-2139 to MANTTASKS-135:
--------------------------------------------------
Affects Version/s: (was: 2.0.2)
(was: 2.0.3)
(was: 2.0.1)
(was: 2.0)
2.0
2.0.1
2.0.2
2.0.3
Component/s: (was: Ant tasks)
Key: MANTTASKS-135 (was: MNG-2139)
Project: Maven 2.x Ant Tasks (was: Maven 2)
> Maven Tasks for Ant should provide an Ant task to launch Maven
> --------------------------------------------------------------
>
> Key: MANTTASKS-135
> URL: http://jira.codehaus.org/browse/MANTTASKS-135
> Project: Maven 2.x Ant Tasks
> Issue Type: Wish
> Affects Versions: 2.0.3, 2.0.2, 2.0.1, 2.0
> Environment: Windows makes this especially troublesome
> Reporter: Dan Fabulich
> Assignee: Brett Porter
>
> Due to bug MNG-2127, it can be tricky to launch Maven from within Ant correctly and extract the correct exit value on all operating systems. A great solution would be to implement a <maven> task in the Maven Tasks for Ant. This code would be able to correctly and simply construct Maven's classpath (using the classes already baked into maven-artifact-ant-*-dep.jar) and execute arbitrary goals on arbitrary POMs.
--
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