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 [email protected] 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: [email protected] For additional commands, e-mail: [email protected]
