You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Bruno Aranda (JIRA)" <de...@myfaces.apache.org> on 2007/05/28 16:51:15 UTC

[jira] Resolved: (TRINIDAD-41) Create more specific "packageContains" configuration attributes for the maven-faces-plugin, for validators and converters

     [ https://issues.apache.org/jira/browse/TRINIDAD-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bruno Aranda resolved TRINIDAD-41.
----------------------------------

    Resolution: Fixed

Implemented in the branch of may

> Create more specific "packageContains" configuration attributes for the maven-faces-plugin, for validators and converters
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TRINIDAD-41
>                 URL: https://issues.apache.org/jira/browse/TRINIDAD-41
>             Project: MyFaces Trinidad
>          Issue Type: New Feature
>          Components: Plugins
>    Affects Versions: 1.0.0-incubating-plugins
>            Reporter: Bruno Aranda
>            Assignee: Bruno Aranda
>             Fix For: 2.0.0-plugins
>
>
> For the myfaces 1.2 build, the implementation artifact needs to include the components, renderkits, converters and validators. The converters and validators, from the api, are in the package "javax.faces", while the renderkits are in "org.apache.myfaces". I need to include all of them in the generated faces-config.xml. 
> The solution, is to create two new configuration attributes (validatorPackageContains and converterPackageContains) that allow to choose the packages for converters/validators without affecting the rest. If these attributes are not set, the value of packageContains is used.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.