You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org> on 2008/10/20 23:58:44 UTC
[jira] Created: (TRINIDAD-1274) The maven faces plug-in creates
duplicate property definitions
The maven faces plug-in creates duplicate property definitions
--------------------------------------------------------------
Key: TRINIDAD-1274
URL: https://issues.apache.org/jira/browse/TRINIDAD-1274
Project: MyFaces Trinidad
Issue Type: Bug
Components: Build
Affects Versions: 1.2.7-plugins, 1.2.8-plugins
Reporter: Andrew Robinson
Assignee: Andrew Robinson
If a component base class has a property and the subclass has the same property, both properties end up being included in the resultant faces-config.xml. So if a component author extends a component and wishes to alter the property-metadata, this is not currently working as both properties will be included. Only the properties in the leaf-most component should be taken, akin to Java inheritance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-1274) The maven faces plug-in creates
duplicate property definitions
Posted by "Andrew Robinson (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Robinson resolved TRINIDAD-1274.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.8-plugins
> The maven faces plug-in creates duplicate property definitions
> --------------------------------------------------------------
>
> Key: TRINIDAD-1274
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1274
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.2.7-plugins, 1.2.8-plugins
> Reporter: Andrew Robinson
> Assignee: Andrew Robinson
> Fix For: 1.2.8-plugins
>
>
> If a component base class has a property and the subclass has the same property, both properties end up being included in the resultant faces-config.xml. So if a component author extends a component and wishes to alter the property-metadata, this is not currently working as both properties will be included. Only the properties in the leaf-most component should be taken, akin to Java inheritance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.