Betreff: Re: Dependency missing on Windows
Hi Robert,
javax.xml.stream was added to the JDK @1.6 (6) - could it be that you
are building locally with a 1.6 JDK whereas your CI server is using 1.5
(which I don't think covers this dependency in the JDK)?
I know you have detailed some info
: Dependency missing on Windows
Thanks for the hint, Brett
I'm pretty sure the buildserver uses 1.4 for compilation because a
Class version error broke the build ;)
But you are right, the server runs a 1.5 JDK and my machine a 1.6. So I
think the build simply doesn't do what I'd expected
robert.kl...@innovations.de wrote at Montag, 20. Juli 2009 08:42:
Hi,
just for the record: I tried with JDK 1.5 on my machine and got the same
dependencies.
as Brian explained, it also depends on the Maven version in use.
- Jörg
An: users@maven.apache.org
Betreff: Re: AW: Dependency missing on Windows
robert.kl...@innovations.de wrote at Montag, 20. Juli 2009 08:42:
Hi,
just for the record: I tried with JDK 1.5 on my machine and got the
same
dependencies.
as Brian explained, it also depends on the Maven
version on all machines.
Thanks all for your help
- Robert
-Ursprüngliche Nachricht-
Von: news [mailto:n...@ger.gmane.org] Im Auftrag von Jörg Schaible
Gesendet: Montag, 20. Juli 2009 09:12
An: users@maven.apache.org
Betreff: Re: AW: Dependency missing on Windows
robert.kl
Not all the internal lists were linkedlists until 2.0.10. That means
the jdk 1.5 vs 1.6 could be causing subtle differences in the
resolution order. Upgrade both to 2.0.10 and you should have
repeatable results that you can use to adjust your pom accordingly.
--Brian (mobile)
On Jul 17,
Hi,
I have a strange experience with a missing dependency. The problem
occurred when upgrading spring-ws-core to version 1.5.7. In that version
they changed a dependency from stax:stax-api to
javax.xml.stream:stax-api.
This change worked fine on my machine (yeah, I know) but broke the build
on
Hi Robert,
javax.xml.stream was added to the JDK @1.6 (6) - could it be that you
are building locally with a 1.6 JDK whereas your CI server is using 1.5
(which I don't think covers this dependency in the JDK)?
I know you have detailed some info contra to that, but it seems the most
likely
