i fought with the same issue, but couldn't find a way to do it with just the
pom. the problem seems deeper, since jaxb 2.0 was internalized and the
plugin now wants jaxb 2.1, the only way to replace jaxb 2.0 is using the
endorsed mechanism. the classpath formed from pom information just can't
beat the jdk itself.
with 1.5 it's even worse: i'm finding i now hafta add activation.jar as well
or i get NoClassDefFoundErrors for javax/activation/DataHandler.
but adding things to endorsed is an "accepted" way of doing business, so
hopefully it'll be an acceptable solution for you as well.
--
View this message in context: http://www.nabble.com/maven-jaxb2-plugin-and-java-1.6-tf4239702.html#a12306492
Sent from the java.net - jaxb users mailing list archive at Nabble.com.