maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2293) maven-plugin-descriptor: Not possible to define a default implementation for a field defined by its interface
Date Sun, 11 Mar 2007 15:05:34 GMT

    [ http://jira.codehaus.org/browse/MNG-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89694
] 

Dennis Lundberg commented on MNG-2293:
--------------------------------------

For this to work you also need new versions of maven-plugin-tools (2.1) and maven-plugin-plugin
(2.3). I'm currently pushing to release theses on the dev list. If the votes go well they
should be available within a week.

> 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
>          Issue Type: New Feature
>          Components: Plugin Creation Tools
>    Affects Versions: 2.0.4
>            Reporter: Jerome Lacoste
>         Assigned To: Kenney Westerhof
>            Priority: Critical
>             Fix For: 2.0.5, 2.1
>
>         Attachments: dependency-mistery.log, it0106.tar.bz2, MNG-2293-plugins.diff, MNG-2293.diff,
MNG-2293.diff, 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 
>  /**@parameter 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

        

Mime
View raw message