[ 
https://issues.apache.org/jira/browse/MYFACES-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498965#comment-13498965
 ] 

Mark Struberg commented on MYFACES-3649:
----------------------------------------

It is perfectly possible to do both in core/impl.

See the ee5 profile I added in core/impl/pom.xml

The trick is to do the 'standard' compile with servlet-3.0 and add an ee5 
profile which we can run in CI. This ee5 profile switches the build to 
servlet-2.5 and excludes the org.apache.myfaces.ee6 package in the 
maven-compiler-plugin configuration.

This works already. I'm now just removing the leftovers which are not used 
anymore.
                
> myfaces-shaded-impl always unpacks myfaces-2.1.1
> ------------------------------------------------
>
>                 Key: MYFACES-3649
>                 URL: https://issues.apache.org/jira/browse/MYFACES-3649
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: build process
>    Affects Versions: 2.2.0, 2.1.9, 2.1.10
>            Reporter: Mark Struberg
>            Assignee: Mark Struberg
>            Priority: Blocker
>         Attachments: myfaces-3649.patch
>
>
> myfaces-shared-impl hardcoded unpacks mf-2.1.1 right now. How can this work?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to