You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/03/25 00:42:16 UTC
[jira] Updated: (MNG-681) Plugin Utility Class
[ http://jira.codehaus.org/browse/MNG-681?page=all ]
Brett Porter updated MNG-681:
-----------------------------
Reporter: Jesse McConnell (was: Jesse McConnell)
> Plugin Utility Class
> --------------------
>
> Key: MNG-681
> URL: http://jira.codehaus.org/browse/MNG-681
> Project: Maven 2
> Type: New Feature
> Components: Plugin API
> Versions: 2.0-alpha-3
> Reporter: Jesse McConnell
> Priority: Minor
>
>
> Tryg mentioned that we might want to make a plugins utility class for some of the issues I ran into implementing a mess of a plugin.
> the plugin was pinned into the process-classes phase and generated a source file which needed to be compiled
> 1) I needed to have the classes that were compiled in the compile phase in my classpath for the plugin. my way around this was to make a URLClassLoader pointed at the compiled classes. The classes I was processing all used one of two interfaces and it would have been nice to have those interfaces available to cast the new instances of the classes and call a method directly. reflection served the purpose though
> 2) I needed to compile the freshly generated source file, so I ripped a mess of code from the maven compiler plugin to achieve this
> two examples of things that would be nice to have a cleaner method of achieving the same results..if you think it is a good idea I can generalize what I did into a couple of api's I think.
--
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