[
https://issues.apache.org/jira/browse/MYFACES-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849354#action_12849354
]
Leonardo Uribe commented on MYFACES-2623:
-----------------------------------------
When you set a dependency as compile and you run jetty, that dependency is
added to your classpath. The minimum dependency version for el is 1.0. All
classes from el api 2.2 should be carefully used to prevent that
ClassNotFoundException.
Historically, the same problem happened when myfaces core had its own portlet
bridge bundled (1.1.x), and when tomahawk added portlet support.
Look the code I committed for ExternalSpecifications, isolating the call to
ValueReference in other class. This issue should be closed as invalid.
> validation-api and el-api 2.2 should be optional dependencies with scope
> compile in myfaces-api
> -----------------------------------------------------------------------------------------------
>
> Key: MYFACES-2623
> URL: https://issues.apache.org/jira/browse/MYFACES-2623
> Project: MyFaces Core
> Issue Type: Bug
> Components: build process
> Affects Versions: 2.0.0-beta-3
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
>
> Currently those two dependencies are defined messy. First they are defined in
> myfaces-core-project as optional which makes no sence since this project is
> just the super-project for api and impl and optional dependencies are not
> transitive. So this has to be removed here.
> Furthermore the definitions of validation-api and el-api in the pom of
> myfaces-api are not completely correct. They should have a scope of compile
> (default) and should have set optional to true instead of just provided or
> provided+optional (which is by the way not allowed).
> After this issue has been resolved el-api 2.2 will be available on the whole
> myfaces-api project, however keep in mind that you are only allowed to use
> the new methods (like getValueReference()) if you checked if the el-api 2.2
> is really available first (via ExternalSpecifications). Otherwise you will
> end up in ClassNotFoundExceptions at runtime when el-api 2.2 is not available
> in the target system.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
