[jira] Commented: (MYFACES-2613) ExternalSpecifications has an import from javax.validation api, and this one should be optional

["Jakob Korherr (JIRA)" <de...@myfaces.apache.org>]

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

Jakob Korherr commented on MYFACES-2613:
----------------------------------------

We should really try to get rid of the redundancy here!

> ExternalSpecifications has an import from javax.validation api, and this one should be optional
> -----------------------------------------------------------------------------------------------
>
>                 Key: MYFACES-2613
>                 URL: https://issues.apache.org/jira/browse/MYFACES-2613
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-314
>    Affects Versions: 2.0.0-beta-3
>            Reporter: Leonardo Uribe
>            Assignee: Jakob Korherr
>             Fix For: 2.0.0-beta-3
>
>
> In a environment without javax.validation api, if bean validation is used,  a ClassNotFoundException is thrown because ExternalSpecifications has an import from javax.validation api. The solution is create another class that has this only import, so ExternalSpecifications could be loaded on the classpath without the presence of javax.validation api.

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