score:0

the warnings about the keystore are not relevant to the exceptions.

the problem is most probably that the failing build is lacking dependencies surrounding com.sun.xml.internal.messaging.saaj.soap.saajmetafactoryimpl. idea probably delivers that dependency. this is possible since internal builds may live in another build environment (classpath/target platform).

the most common reasons for noclassdeffounderrors are exceptions thrown in static initializers of referenced classes (exceptionininitializer as root cause) and classnotfoundexceptions for referenced classes. the latter is what would happen if a dependency of the saajmetafactoryimpl is missing, but not the library with the factoryimpl itself.

i suspect the exception contains another caused-by chain link which in turn contains the root cause of that exception, mentioning the actually missing class. maybe you can reconfigure the build to display the complete cause-chain of thrown exceptions.

in general, try to compare the two build environments with respect to the target platforms they use to resolve dependencies. this makes the missing libraries obvious.


Related Query

More Query from same tag