NB: majority of source jars on ibiblio and repo1 are
MANIFEST only jars..which means whomever is building and deploying is not
grabbing source and compiling
possible branch deadlock going on if Dan has it checked out..you *should* have
been notified of a deadlock when you committed your update...so..did you commit
your change to XmlSchemaBundleTest.java?
which source tree are you pulling from?
do a ls -al on the folder...is there an accessible .SVN folder in that source
folder?
if so what do the tags in .SVN say who was the latest to touch
org.apache.ws.xmlschema.bundletest.XmlSchemaBundleTest.java?
..let me know..
Thanks Mike,
Martin
> Date: Wed, 1 Oct 2014 10:01:51 -0400
> Subject: Re:
> From: [email protected]
> To: [email protected]
>
> That's strange ... I got the code I patched from the svn trunk of
> Apache XML Schema. I assumed Dan Kulp was making some changes to add
> my xmlschema-walker enhancement.
>
> Thanks,
> Mike
>
> On Wed, Oct 1, 2014 at 9:42 AM, Martin Gainty <[email protected]> wrote:
> >
> >
> > Date: Tue, 30 Sep 2014 22:07:15 -0400
> > Subject:
> > From: [email protected]
> > To: [email protected]
> >
> > 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()
> >
> > .groupId("org.apache.ws.xmlschema").artifactId("xmlschema-walker").versionAsInProject()));
> >
> > (2) CoreOptions.provision(CoreOptions.mavenBundle()
> >
> > .groupId("org.apache.ws.xmlschema").artifactId("xmlschema-walker").version("2.2.1-SNAPSHOT")));
> >
> > I tried the first one and it gave me this error:
> >
> > -----
> > Running org.apache.ws.xmlschema.bundletest.XmlSchemaBundleTest
> > SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> > SLF4J: Defaulting to no-operation (NOP) logger implementation
> > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for
> > further details.
> > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.45
> > sec <<< FAILURE! - in
> > org.apache.ws.xmlschema.bundletest.XmlSchemaBundleTest
> > initializationError(org.apache.ws.xmlschema.bundletest.XmlSchemaBundleTest)
> > Time elapsed: 0.061 sec <<< ERROR!
> > java.lang.reflect.InvocationTargetException: null
> > at
> > org.ops4j.pax.exam.MavenUtils.getFileFromClasspath(MavenUtils.java:117)
> > at org.ops4j.pax.exam.MavenUtils.getArtifactVersion(MavenUtils.java:61)
> > at org.ops4j.pax.exam.MavenUtils$1.getVersion(MavenUtils.java:89)
> > at
> > org.ops4j.pax.exam.options.MavenArtifactUrlReference.version(MavenArtifactUrlReference.java:86)
> > at
> > org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(MavenArtifactUrlReference.java:90)
> > at
> > org.ops4j.pax.exam.options.MavenArtifactUrlReference.versionAsInProject(MavenArtifactUrlReference.java:31)
> > at
> > org.ops4j.pax.exam.options.MavenArtifactProvisionOption.versionAsInProject(MavenArtifactProvisionOption.java:91)
> > at
> > org.apache.ws.xmlschema.bundletest.XmlSchemaBundleTest.configuration(XmlSchemaBundleTest.java:41)
> > -----
> > MG>Hi Mike
> > MG>http://svn.apache.org/viewvc/webservices/xmlschema/tags/xmlschema-2.0.3/xmlschema-bundle-test/src/test/java/org/apache/ws/xmlschema/bundletest/XmlSchemaBundleTest.java?revision=1365578&view=co
> > MG>shows no configuration method.. and.. the last person to touch
> > XmlSchemaBundleTest.java source was Dan Kulp 2 years ago
> > MG>where are you pulling this from?
> > MG>Thanks,
> >
> > 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.
> >
> > Thanks,
> > Mike
> >
> >
> > --------------------------------------------------------------------- To
> > unsubscribe, e-mail: [email protected] For additional commands,
> > e-mail: [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>