You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/27 21:42:55 UTC
[jira] Moved: (MANTTASKS-171) contribution: PluginClasspathTask
(renamed from PluginDependencyTask)
[ http://jira.codehaus.org/browse/MANTTASKS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl moved MNG-2329 to MANTTASKS-171:
----------------------------------------------
Complexity: (was: Intermediate)
Component/s: (was: Artifacts and Repositories)
Fix Version/s: (was: 3.x)
Key: MANTTASKS-171 (was: MNG-2329)
Project: Maven 2.x Ant Tasks (was: Maven 2 & 3)
> contribution: PluginClasspathTask (renamed from PluginDependencyTask)
> ---------------------------------------------------------------------
>
> Key: MANTTASKS-171
> URL: http://jira.codehaus.org/browse/MANTTASKS-171
> Project: Maven 2.x Ant Tasks
> Issue Type: New Feature
> Reporter: Erik Romson
> Attachments: maven-artifact-ant.zip
>
>
> I need to run ant tasks outside of maven2, because we use ant to populate databases, generate reports etc from the database. Without going into any discussions on the appropriate usage of ant, I needed to be able to get hold of the classpath for plugins. I made a task for it.
> Copy - paste of DependencyTask basically.
--
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