I think we should still provide it ourselfs.
Given that this is not only thing we provide that is already part of JDK
(java activation for instance)
This provides us a way to override jdk provided stuff with ours that can
come handy if we need to patch it in any way.
--
tomaz
On Wed, Jul 17, 2013 at 4:04 PM, Shelly McGowan <smcgowan(a)redhat.com> wrote:
This is the JIRA that provoked this query:
https://issues.jboss.org/browse/JBCTS-1294
Shelly
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: wildfly-dev(a)lists.jboss.org
Sent: Wednesday, July 17, 2013 9:52:01 AM
Subject: [wildfly-dev] JAXB APIs and Wildfly
With JAXB APIs now part of Java SE 7 and Java SE 7 being the minimum
requirement for Wildfly, are there plans to remove the explicit
dependency of org.jboss.spec.javax.xml.bind:jboss-jaxb-api_2.2_spec and
com.sun.xml.bind:jaxb-impl?
Would it be more appropriate to include these packages are part of the
javax.api module?
Shelly McGowan
JBoss, by Red Hat
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev