You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mark Struberg (JIRA)" <de...@myfaces.apache.org> on 2010/06/29 11:34:51 UTC

[jira] Resolved: (EXTCDI-27) shade extcdi-jsf12 artifact into extcdi-jsf20 artifact

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

Mark Struberg resolved EXTCDI-27.
---------------------------------

    Fix Version/s: 1.0.0-SNAPSHOT
       Resolution: Fixed

initial setup is done. It might be necessary to exclude some classes from getting shaded into the JSF-2 artifact if they are supposed to work in JSF-1 only.

> shade extcdi-jsf12 artifact into extcdi-jsf20 artifact
> ------------------------------------------------------
>
>                 Key: EXTCDI-27
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-27
>             Project: MyFaces CODI
>          Issue Type: Improvement
>          Components: JEE-JSF20-Module
>    Affects Versions: 1.0.0-SNAPSHOT
>            Reporter: Mark Struberg
>             Fix For: 1.0.0-SNAPSHOT
>
>
> Currently we have 3 main modules (each with api + impl): core, jsf12 and jsf20
> The jsf12 module contains only code that runs on JSF-1.1 and JSF-1.2 environments but does not need any definitions which are only available in JSF-2.0 (like e.g. the ViewMap, various JSF annotations, etc).
> The jsf20 module otoh contains sources which _only_ run on JSF-2 and will not run on JSF-1.x.
> To have a clear distinction for the end-users, we shall utilise the maven-shade-plugin to reuse the code in the jsf12 module for the jsf20 module. So in the end, a user will either add a dependency to the jsf12 module or the jsf20 module where he will get all the reusable bits from the jsf12 sources in the extcdi-jsf20.jar

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