You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/01/06 17:10:19 UTC
[jira] Created: (MNG-3971) Provide parity in features between
native ant-mojo support and antrun plugin
Provide parity in features between native ant-mojo support and antrun plugin
----------------------------------------------------------------------------
Key: MNG-3971
URL: http://jira.codehaus.org/browse/MNG-3971
Project: Maven 2
Issue Type: Improvement
Components: Plugin API, Plugins and Lifecycle
Affects Versions: 2.1.0-M1, 2.0.9
Reporter: John Casey
In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven.
The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive.
--
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
[jira] Closed: (MNG-3971) Provide parity in features between native
ant-mojo support and antrun plugin
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey closed MNG-3971.
---------------------------
Resolution: Fixed
This will require releases of:
* plexus-ant-factory 1.0-alpha-2.1 (https://svn.codehaus.org/plexus/plexus-component-factories/branches/plexus-ant-factory-1.0-alpha-2.x)
* maven-plugin-tools 2.4.4 (or, maybe 2.5 for this sort of change) (https://svn.apache.org/repos/asf/maven/plugin-tools/trunk)
> Provide parity in features between native ant-mojo support and antrun plugin
> ----------------------------------------------------------------------------
>
> Key: MNG-3971
> URL: http://jira.codehaus.org/browse/MNG-3971
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API, Plugins and Lifecycle
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1.0
>
>
> In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven.
> The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive.
--
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
[jira] Updated: (MNG-3971) Provide parity in features between
native ant-mojo support and antrun plugin
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-3971:
----------------------------
Assignee: John Casey
Fix Version/s: 2.1.0-M2
I'm assigning this to 2.1.0-M2 since it needs attention, but this may need to shift in the future if other things come up. I don't want to get in the way of the release timeline for 2.1.0-M2.
> Provide parity in features between native ant-mojo support and antrun plugin
> ----------------------------------------------------------------------------
>
> Key: MNG-3971
> URL: http://jira.codehaus.org/browse/MNG-3971
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API, Plugins and Lifecycle
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1.0-M2
>
>
> In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven.
> The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive.
--
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
[jira] Updated: (MNG-3971) Provide parity in features between
native ant-mojo support and antrun plugin
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3971:
------------------------------
Fix Version/s: (was: 2.1.0-M2)
2.1.0-M3
bumping per John's comment above
> Provide parity in features between native ant-mojo support and antrun plugin
> ----------------------------------------------------------------------------
>
> Key: MNG-3971
> URL: http://jira.codehaus.org/browse/MNG-3971
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API, Plugins and Lifecycle
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1.0-M3
>
>
> In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven.
> The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive.
--
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
[jira] Commented: (MNG-3971) Provide parity in features between
native ant-mojo support and antrun plugin
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160102#action_160102 ]
John Casey commented on MNG-3971:
---------------------------------
Probably the simplest way to inject classpaths is to mod the plugin tools that create the plugin descriptors for ant-mojos, injecting these as parameters...then, also modding the plugin support to actually do the injection using information that can be gleaned from Project, etc. information.
> Provide parity in features between native ant-mojo support and antrun plugin
> ----------------------------------------------------------------------------
>
> Key: MNG-3971
> URL: http://jira.codehaus.org/browse/MNG-3971
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API, Plugins and Lifecycle
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1.0-M2
>
>
> In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven.
> The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive.
--
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
[jira] Work started: (MNG-3971) Provide parity in features between
native ant-mojo support and antrun plugin
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MNG-3971 started by John Casey.
> Provide parity in features between native ant-mojo support and antrun plugin
> ----------------------------------------------------------------------------
>
> Key: MNG-3971
> URL: http://jira.codehaus.org/browse/MNG-3971
> Project: Maven 2
> Issue Type: Improvement
> Components: Plugin API, Plugins and Lifecycle
> Affects Versions: 2.0.9, 2.1.0-M1
> Reporter: John Casey
> Assignee: John Casey
> Fix For: 2.1.0
>
>
> In particular, we need to make sure classpaths, etc. that are available in the antrun plugin are made available in the ant-mojo support. Going forward, it'd be nice to find a way to use a common module for the two ways of using Ant inside Maven.
> The features available in the Antrun Plugin are often confused with those available in the ant-mojo support, so this feature parity is critical to make Ant usage in Maven more intuitive.
--
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