[Taking this back to the list so they know you have found the problem.]
Good to hear you found the cause. I can confirm that AFAIK javax.xml.ws is not present in Java 5.
On 04/08/10 21:57, Jon Strayer wrote:
Sorry, I thought I mentioned it but it's a compilation failure: package javax.xml.ws does not exist. Duh, I was using Java 6 on my laptop and Java 5 on the server. Eclipse is using JDK 5 so it must be that the javax.xml.ws<http://javax.xml.ws> package moved into Java SE. Anyway, thanks. On Wed, Aug 4, 2010 at 1:38 AM, Ben Caradoc-Davies<[email protected]> wrote: Try "mvn --version" on both and look for differences in Java version and Maven. For example, if you inadvertently used Java 6 API elements on your laptop and your server builds with Java 5 the build will fail. There are also differences between Maven versions that can have unexpected side-effects. What is the nature of the failure? Compile or test? On 04/08/10 05:04, Jon Strayer wrote: I have a problem where my maven build works fine on my laptop but compilation fails on the build server. I've already blown away both local repositories but that didn't help. I ran help:effective-pom on both but there are no unexpected differences. Do you have any idea what else I should look at? The fact that the build fails isn't the problem. That fact that it succeeds one place and fails on the other is. -- Ben Caradoc-Davies<[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- " People who couldn't find Nebraska on a world map are certain that global warming is a left-wing hoax. Gene Lyons"
-- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
