[ http://jira.codehaus.org/browse/MNG-2293?page=all ]
Jerome Lacoste updated MNG-2293:
--------------------------------
Attachment: MNG-2293-plugins.diff
dependency-mistery.log
MNG-2293.diff
> maven-plugin-descriptor: Not possible to define a default implementation for
> a field defined by its interface
> -------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2293
> URL: http://jira.codehaus.org/browse/MNG-2293
> Project: Maven 2
> Type: New Feature
> Components: Plugin Creation Tools
> Versions: 2.0.4
> Reporter: Jerome Lacoste
> Priority: Critical
> Attachments: MNG-2293-plugins.diff, MNG-2293.diff, dependency-mistery.log,
> it0106.tar.bz2, patch-MNG-2293-source2.tar.bz2, patch-MNG-2293.diff
>
>
> MOJO-393 is about letting the user define an alternate configuration element,
> thus changing the way the webstart plugin works.
> For that the idea was to make the mojo field an interface, provide a default
> implementation in the plugin and let the user use plexus to instanciate a new
> implemenation.
> so for most users we would have:
> <configuration>
> <bla>
> </bla>
> </configuration>
> and for some:
> <configuration>
> <bla implementation="com....bla">
> </bla>
> </configuration>
> Unfortunately, today I am forced to specify the implementation in both cases.
> There's no way to inform the plugin to use the default implementation.
> The plugin.xml contains:
> <parameter>
> <name>bla</name>
> <type>...BlaInterface</type> <!-- that will fail -->
> ...
> </parameter>
> I tried to use
> /[EMAIL PROTECTED] implementation="...BlaImplementation"*/
> BlaInterface bla;
> but that fails as well.
> Marking critical because it doesn't allow me add new features to the plugin
> without breaking the config.xml.
--
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