You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ro...@innovations.de on 2009/07/17 15:46:44 UTC
Dependency missing on Windows
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 our ci server, as the new dependency resolved to stax-api-1.0-2.jar
which is built with Java 1.5 and not 1.4 (which we unfortunately must
support).
The interesting thing: when calling mvn dependency:tree on the server
showed the dependency but it did not appear on my machine
This of course would explain, why the build worked locally.
Can anybody explain this difference in dependency resolution?
Some details
- The server is running Linux with Maven 2.0.9 and Java 1.5
- I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with same
result) and Java 1.6
- Same Repositories
- Server and Windows should use Java 1.4 for building
- It is mulit-module project
- In the project is a transitive dependency to stax:stax-api in version
1.0.1 (this version was used by spring-ws-core before the upgrade)
Cheers,
Robert Klaus
Business Rules Management
--
Innovations Software Technology GmbH
Bosch Group
Ziegelei 7, 88090 Immenstaad/GERMANY
Tel. +49 7545 202-339
Fax +49 7545 202-301
robert.klaus@innovations.de
www.innovations.de
Executives: Achim Berger, Thomas Cotic, Walter Pitz, Thomas Schmid
Register Court Ulm HRB 631888
This message may contain confidential and privileged information. Any
unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please inform us immediately and
destroy this message including all copies thereof.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Re: AW: Dependency missing on Windows
Posted by Stephen Connolly <st...@gmail.com>.
And if the maven version is < 2.0.10, then even using the same JDK version
may result in a different dependency order if you are on a different
architecture
2009/7/20 <Ro...@innovations.de>
> Hi,
>
> that's also good to know. It would be best to run the build with the same
> JDK and Maven version on all machines.
>
> Thanks all for your help
>
> - Robert
>
> > -----Ursprüngliche Nachricht-----
> > Von: news [mailto:news@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.Klaus@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
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
AW: Re: AW: Dependency missing on Windows
Posted by Ro...@innovations.de.
Hi,
that's also good to know. It would be best to run the build with the same JDK and Maven version on all machines.
Thanks all for your help
- Robert
> -----Ursprüngliche Nachricht-----
> Von: news [mailto:news@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.Klaus@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
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
Re: AW: Dependency missing on Windows
Posted by Jörg Schaible <jo...@gmx.de>.
Robert.Klaus@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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: Dependency missing on Windows
Posted by Ro...@innovations.de.
Hi,
just for the record: I tried with JDK 1.5 on my machine and got the same dependencies.
Cheers,
Robert
> -----Ursprüngliche Nachricht-----
> Von: Robert.Klaus@innovations.de [mailto:Robert.Klaus@innovations.de]
> Gesendet: Montag, 20. Juli 2009 08:29
> An: users@maven.apache.org
> Betreff: AW: 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. It seems to me,
> that the JDK is used for the dependency resolution. If so, this would
> explain the difference between my machine and the server.
>
> I will check that.
>
> Cheers,
>
> Robert
>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Brett Randall [mailto:javabrett@gmail.com]
> > Gesendet: Samstag, 18. Juli 2009 01:30
> > An: Maven Users List
> > 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 contra to that, but it seems the
> > most
> > likely reason to me. Either way I'm pretty sure this dep is not in
> JDK
> > 1.4 on your server, which would explain the missing dep. Double-
> check
> > your local/remote build JDKs.
> >
> > Best
> > Brett
> >
> >
> > Robert.Klaus@innovations.de wrote:
> > > 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 our ci server, as the new dependency resolved to stax-api-1.0-
> > 2.jar
> > > which is built with Java 1.5 and not 1.4 (which we unfortunately
> must
> > > support).
> > >
> > > The interesting thing: when calling mvn dependency:tree on the
> server
> > > showed the dependency but it did not appear on my machine
> > >
> > > This of course would explain, why the build worked locally.
> > >
> > > Can anybody explain this difference in dependency resolution?
> > >
> > > Some details
> > > - The server is running Linux with Maven 2.0.9 and Java 1.5
> > > - I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with
> > same
> > > result) and Java 1.6
> > > - Same Repositories
> > > - Server and Windows should use Java 1.4 for building
> > > - It is mulit-module project
> > > - In the project is a transitive dependency to stax:stax-api in
> > version
> > > 1.0.1 (this version was used by spring-ws-core before the upgrade)
> > >
> > > Cheers,
> > >
> > > Robert Klaus
> > > Business Rules Management
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
AW: Dependency missing on Windows
Posted by Ro...@innovations.de.
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. It seems to me, that the JDK is used for the dependency resolution. If so, this would explain the difference between my machine and the server.
I will check that.
Cheers,
Robert
> -----Ursprüngliche Nachricht-----
> Von: Brett Randall [mailto:javabrett@gmail.com]
> Gesendet: Samstag, 18. Juli 2009 01:30
> An: Maven Users List
> 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 contra to that, but it seems the
> most
> likely reason to me. Either way I'm pretty sure this dep is not in JDK
> 1.4 on your server, which would explain the missing dep. Double-check
> your local/remote build JDKs.
>
> Best
> Brett
>
>
> Robert.Klaus@innovations.de wrote:
> > 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 our ci server, as the new dependency resolved to stax-api-1.0-
> 2.jar
> > which is built with Java 1.5 and not 1.4 (which we unfortunately must
> > support).
> >
> > The interesting thing: when calling mvn dependency:tree on the server
> > showed the dependency but it did not appear on my machine
> >
> > This of course would explain, why the build worked locally.
> >
> > Can anybody explain this difference in dependency resolution?
> >
> > Some details
> > - The server is running Linux with Maven 2.0.9 and Java 1.5
> > - I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with
> same
> > result) and Java 1.6
> > - Same Repositories
> > - Server and Windows should use Java 1.4 for building
> > - It is mulit-module project
> > - In the project is a transitive dependency to stax:stax-api in
> version
> > 1.0.1 (this version was used by spring-ws-core before the upgrade)
> >
> > Cheers,
> >
> > Robert Klaus
> > Business Rules Management
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Dependency missing on Windows
Posted by Brett Randall <ja...@gmail.com>.
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 reason to me. Either way I'm pretty sure this dep is not in JDK
1.4 on your server, which would explain the missing dep. Double-check
your local/remote build JDKs.
Best
Brett
Robert.Klaus@innovations.de wrote:
> 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 our ci server, as the new dependency resolved to stax-api-1.0-2.jar
> which is built with Java 1.5 and not 1.4 (which we unfortunately must
> support).
>
> The interesting thing: when calling mvn dependency:tree on the server
> showed the dependency but it did not appear on my machine
>
> This of course would explain, why the build worked locally.
>
> Can anybody explain this difference in dependency resolution?
>
> Some details
> - The server is running Linux with Maven 2.0.9 and Java 1.5
> - I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with same
> result) and Java 1.6
> - Same Repositories
> - Server and Windows should use Java 1.4 for building
> - It is mulit-module project
> - In the project is a transitive dependency to stax:stax-api in version
> 1.0.1 (this version was used by spring-ws-core before the upgrade)
>
> Cheers,
>
> Robert Klaus
> Business Rules Management
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Dependency missing on Windows
Posted by "Brian E. Fox" <br...@infinity.nu>.
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, 2009, at 9:46 AM, <Ro...@innovations.de> wrote:
> 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 our ci server, as the new dependency resolved to stax-api-1.0-2.jar
> which is built with Java 1.5 and not 1.4 (which we unfortunately must
> support).
>
> The interesting thing: when calling mvn dependency:tree on the server
> showed the dependency but it did not appear on my machine
>
> This of course would explain, why the build worked locally.
>
> Can anybody explain this difference in dependency resolution?
>
> Some details
> - The server is running Linux with Maven 2.0.9 and Java 1.5
> - I'm using Windows XP with Maven 2.1.0 (but also tried 2.0.9 with
> same
> result) and Java 1.6
> - Same Repositories
> - Server and Windows should use Java 1.4 for building
> - It is mulit-module project
> - In the project is a transitive dependency to stax:stax-api in
> version
> 1.0.1 (this version was used by spring-ws-core before the upgrade)
>
> Cheers,
>
> Robert Klaus
> Business Rules Management
> --
> Innovations Software Technology GmbH
> Bosch Group
> Ziegelei 7, 88090 Immenstaad/GERMANY
> Tel. +49 7545 202-339
> Fax +49 7545 202-301
> robert.klaus@innovations.de
> www.innovations.de
>
> Executives: Achim Berger, Thomas Cotic, Walter Pitz, Thomas Schmid
> Register Court Ulm HRB 631888
> This message may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited. If
> you are not the intended recipient, please inform us immediately and
> destroy this message including all copies thereof.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org