e
used.
Regards,
Paul Golick
e-mail: [EMAIL PROTECTED]
Jeremy Boynes <[EMAIL PROTECTED]>
2007-02-13 05:30 PM
Please respond to
tuscany-dev@ws.apache.org
To
tuscany-dev@ws.apache.org
cc
Subject
Re: SDO impl Java 6 dependancy
It's not a dependency on Java6, it'
ny-dev@ws.apache.org
To
tuscany-dev@ws.apache.org
cc
Subject
Re: SDO impl Java 6 dependancy
It's not a dependency on Java6, it's a dependency on StAX
(java.xml.stream). That happens to be included in Java6, but it is
also included in Java5 Enterprise Edition and is available separately
It's not a dependency on Java6, it's a dependency on StAX
(java.xml.stream). That happens to be included in Java6, but it is
also included in Java5 Enterprise Edition and is available separately
for use on Java5 Standard Edition and J2SE 1.4.
It seems the SDO implementation now has a hard r
By compiling with a jar that has Java 6 dependancy we are ourselves creating
a dependancy on Java 6 for the SDO impl jar. This seems to be a problem to
me. No ?
Robbie
On 2/13/07, Yang ZHONG <[EMAIL PROTECTED]> wrote:
sdo/impl/pom.xml declares dependency on stax-api, that's required to
sdo/impl/pom.xml declares dependency on stax-api, that's required to compile
sdo impl.
StAX impl will be required for runtime if StAX support code path is
executed.
On 2/13/07, Robbie Minshall <[EMAIL PROTECTED]> wrote:
Paul identified a problem in
https://issues.apache.org/jira/browse/TUSCANY
Paul identified a problem in
https://issues.apache.org/jira/browse/TUSCANY-1105 which appears to indicate
that the sdo impl jar has dependancies upon Java 6 for some code paths.
This scneario is not limited to the CTS execution but should probably
present itSelf at least when using the
org.apache.
