You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2015/09/06 22:45:26 UTC

[jira] [Closed] (MANTTASKS-171) contribution: PluginClasspathTask (renamed from PluginDependencyTask)

     [ https://issues.apache.org/jira/browse/MANTTASKS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MANTTASKS-171.
------------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> contribution: PluginClasspathTask (renamed from PluginDependencyTask)
> ---------------------------------------------------------------------
>
>                 Key: MANTTASKS-171
>                 URL: https://issues.apache.org/jira/browse/MANTTASKS-171
>             Project: Maven 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 was sent by Atlassian JIRA
(v6.3.4#6332)