ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Pigott <>
Subject [No Subject]
Date Wed, 01 Oct 2014 02:07:15 GMT
Hi WS Developers,

 I looked at the OSGi build failure for Apache XML Schema and I have a
"fix" ... I'll put
it in quotes because it's more paper clips and duct tape than anything
else.  I looked on the internet, and it gave two recommendations:

(1) CoreOptions.provision(CoreOptions.mavenBundle()


(2) CoreOptions.provision(CoreOptions.mavenBundle()


I tried the first one and it gave me this error:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See for
further details.
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.45
sec <<< FAILURE! - in
 Time elapsed: 0.061 sec  <<< ERROR!
java.lang.reflect.InvocationTargetException: null
    at org.ops4j.pax.exam.MavenUtils.getFileFromClasspath(
    at org.ops4j.pax.exam.MavenUtils.getArtifactVersion(
    at org.ops4j.pax.exam.MavenUtils$1.getVersion(
    at org.ops4j.pax.exam.options.MavenArtifactUrlReference.version(
    at org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(
    at org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(
    at org.ops4j.pax.exam.options.MavenArtifactProvisionOption.versionAsInProject(

However, the second one succeeds, which I attached a patch for.  I
hope it's just because the xmlschema-walker code hasn't made it into
the Maven repository yet, because I'm not sure what else it would be.


View raw message