[
https://jira.codehaus.org/browse/MNG-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MNG-2293:
-------------------------------
Description:
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:
{code:xml}<configuration>
<bla>
</bla>
</configuration>{code}
and for some:
{code:xml}<configuration>
<bla implementation="com....bla">
</bla>
</configuration>{code}
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:
{code:xml} <parameter>
<name>bla</name>
<type>...BlaInterface</type> <!-- that will fail -->
...
</parameter>{code}
I tried to use
{code:java} /**@parameter implementation="...BlaImplementation"*/
BlaInterface bla;{code}
but that fails as well.
Marking critical because it doesn't allow me add new features to the plugin
without breaking the config.xml.
was:
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.
> maven-plugin-descriptor: Not possible to define a default implementation for
> a field defined by its interface
> -------------------------------------------------------------------------------------------------------------
>
> Key: MNG-2293
> URL: https://jira.codehaus.org/browse/MNG-2293
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Sites & Reporting
> Affects Versions: 2.0.4
> Reporter: Jerome Lacoste
> Assignee: Kenney Westerhof
> Priority: Critical
> Fix For: 2.0.5
>
> Attachments: dependency-mistery.log, it0106.tar.bz2, MNG-2293.diff,
> MNG-2293.diff, MNG-2293-plugins.diff, patch-MNG-2293.diff,
> patch-MNG-2293-source2.tar.bz2
>
>
> 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:
> {code:xml}<configuration>
> <bla>
> </bla>
> </configuration>{code}
> and for some:
> {code:xml}<configuration>
> <bla implementation="com....bla">
> </bla>
> </configuration>{code}
> 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:
> {code:xml} <parameter>
> <name>bla</name>
> <type>...BlaInterface</type> <!-- that will fail -->
> ...
> </parameter>{code}
> I tried to use
> {code:java} /**@parameter implementation="...BlaImplementation"*/
> BlaInterface bla;{code}
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
