Thanks a lot for your replies. This solved my problem.
This is what we did.
We've added JAXP 1.3.2 to our internal repo using the following POM (by
executing 'mvn deploy'):
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=
bundles are usually a bad idea because conflict with dependencies
needed by other projects
jaxp 1.4 is in
http://repo1.maven.org/maven2/javax/xml/parsers/jaxp-api/1.4/
and Sun's reference implementation in
http://repo1.maven.org/maven2/com/sun/xml/parsers/jaxp-ri/1.4/
On 2/19/07, Erik Ruisma
You could make your own bundle pom by creating a new pom with
packaging pom and specify the dependencies/libraries used by JWSDP
etc.
So you would make your own JWSDP v 1.4, 1.6, 2.0 etc poms with the
proper dependencies declared and then deploy those poms to your
internal corporate repo, and