[
https://issues.apache.org/jira/browse/BVAL-69?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12880307#action_12880307
]
Donald Woods commented on BVAL-69:
----------------------------------
I think we need to also fix some package names, as bval-xstream provides
classes in o.a.bval.routines and o.a.bval.xml, while bval-core provides some
classes in o.a.bval.routines also. It's not critical right now, since
bval-xstream is not a bundle, but for proper packaging best practices, we
should clean this up....
> make dependency to com.thoughtworks.xstream of bval-core optional or obsolete
> -----------------------------------------------------------------------------
>
> Key: BVAL-69
> URL: https://issues.apache.org/jira/browse/BVAL-69
> Project: BeanValidation
> Issue Type: Improvement
> Components: jsr303
> Affects Versions: 0.2-incubating
> Reporter: Roman Stumm
> Assignee: Roman Stumm
> Fix For: 0.2-incubating
>
>
> currently bval-core needs xstream to compile, although xstream is NOT used to
> marshal XML when working with bval-jsr303 xml-descriptors. Only proprietary
> xml-support in bval-core uses xstream.
> To minimize the number of different XML-frameworks (bval-jsr303 has a
> dependency to jaxb, which is OK, because this is part of the JDK) and to
> minimize the number of dependencies in general, we should refactor the
> core-classes to get rid of the mandatory xstream dependency.
> A first simple way would be to remove all XStream annotation in
> org.apache.bval.xml and instead use the programmatic API of XStream to define
> the mapping and move the xstream-dependent code to a new optional mvn-module.
> Another way could be to change the code from using XStream to using jaxb or
> to remove the code (if we do not want to keep the proprietary functionality,
> which is not required for the jsr303 features)
> Any other ideas??
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
