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

Jakob Korherr commented on MYFACES-2623:
----------------------------------------

I could not find any problems with this configuration in any server, so I 
committed the code.

If you have any further concerns, please read the maven documentation of 
optional first: 
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html

> 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
>             Fix For: 2.0.0-beta-4
>
>
> 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.

Reply via email to