[
https://issues.apache.org/jira/browse/MYFACES-3649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13498702#comment-13498702
]
Mark Struberg commented on MYFACES-3649:
----------------------------------------
This can only properly get resolved by removing the cycle.
Currently the ee6 module only contains the MyFacesContainerInitializer.
It is perfectly fine to keep this in core-impl as this class will not even get
loaded.
Upgrading core-impl to servlet-3.0 is also much easier than doing all this
dirty hacks.
We already effectively ship the ServletContainerInitializer with our jars since
2.0.5 anyway. So what?
We might think about adding a CI profile which excludes the ee6 package and
compiles with servlet-2.5.
The clean alternative would be to keep core-impl servlet-2.5 and ship an
additional artifact for ee6.
> 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
>
> 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
