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 2006/05/31 02:49:43 UTC

[jira] Updated: (MNG-2333) Plugins need to offer up all information without executing

     [ http://jira.codehaus.org/browse/MNG-2333?page=all ]

Jason van Zyl updated MNG-2333:
-------------------------------

    Description: 
In an IDE environment, you want to know what will be generated by a plugin without having it execute. For example, if you have a plugin that generates a source directory you want to know that without having actually execute the plugin because it can take a long time if you have a lot of plugins.

Another issue will probably have to be created to outline changes to the plugin api so that external tools can call this method to get all the information up-front. I couldn't find any related issues.

This should also work when reactor projects are run.


  was:
In an IDE environment, you want to know what will be generated by a plugin without having it execute. For example, if you have a plugin that generates a source directory you want to know that without having actually execute the plugin because it can take a long time if you have a lot of plugins.

Another issue will probably have to be created to outline changes to the plugin api so that external tools can call this method to get all the information up-front. I couldn't find any related issues.



> Plugins need to offer up all information without executing
> ----------------------------------------------------------
>
>          Key: MNG-2333
>          URL: http://jira.codehaus.org/browse/MNG-2333
>      Project: Maven 2
>         Type: New Feature

>   Components: Embedding
>     Versions: 2.0.5
>     Reporter: Jason van Zyl
>     Assignee: Jason van Zyl

>
>
> In an IDE environment, you want to know what will be generated by a plugin without having it execute. For example, if you have a plugin that generates a source directory you want to know that without having actually execute the plugin because it can take a long time if you have a lot of plugins.
> Another issue will probably have to be created to outline changes to the plugin api so that external tools can call this method to get all the information up-front. I couldn't find any related issues.
> This should also work when reactor projects are run.

-- 
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