[
https://issues.apache.org/jira/browse/BVAL-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870082#action_12870082
]
Donald Woods commented on BVAL-1:
---------------------------------
Not sure I follow what you're proposing....
What exactly do we gain by splitting our implementation into a api and impl?
There is a spec api that defines the API for anyone wanting to provide an impl,
so doesn't that fit your idea of api vs. impl? Is there some OSGi specific
packaging/best practices that you're wanting to follow?
>From a recent email thread about moving constraints - The spec defines
>constraints that all implementations must provide, but we can provide
>additional ones. Why would we move these out?
> split usable validations like @Emain from our impl
> --------------------------------------------------
>
> Key: BVAL-1
> URL: https://issues.apache.org/jira/browse/BVAL-1
> Project: BeanValidation
> Issue Type: Improvement
> Reporter: Mark Struberg
> Assignee: Mark Struberg
>
> Currently there are a few very useful Validations included in the impl.
> Since they are in fact independent of the actual JSR-303 implementation, we
> should split them out into two own modules
> * validators-api which contains only the annotations and public stuff
> * validators-impl which contains the implementation stuff which are not
> needed at compile time (always used with <scope>runtime</scope>)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
