Thanks for the feedback! It seems I can in fact ignore the problem and just run eyeball. I did have to apply a little magic using either: http://timhodson.com/2011/06/running-jena-eyeball-on-mac-osx/
or java -cp "lib/*" jena.eyeball -check FOO Now for some validation fun! On Mon, Dec 15, 2014 at 6:32 AM, Andy Seaborne <[email protected]> wrote: > > On 14/12/14 14:31, Nate Marks wrote: > >> I'd like to try to use eyeball as sort of a learning tool, but when I >> download the eyeball 2.3 zip and run ant test, I get the following >> failure. >> > > The last release of Eyeball was pre-Apache. > > The code is at: > > https://svn.apache.org/repos/asf/jena/Scratch/Eyeball/trunk/ > > and it is maven based. (well, it has pom.xml not build.xml!) > > >> [junit] >> [junit] Testcase: warning(junit.framework.TestSuite$1): FAILED >> [junit] Class >> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no >> public constructor TestCase(String name) or TestCase() >> [junit] junit.framework.AssertionFailedError: Class >> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector has no >> public constructor TestCase(String name) or TestCase() >> [junit] >> [junit] >> > > Those look like it is being run with JUnit3 ... but the annotations style > is Junit4. This an ant-setup thing, I think. > > >> >> This class is different from all the others , notably because it uses >> >> @RunWith(Parameterized.class) public class TestMoreOwlSyntaxInspector >> extends InspectorTestBase >> >> as opposed to : >> >> @RunWith(JUnit4.class) public class TestLiteralInspector extends >> InspectorTestBase >> >> Unfortunately , I'm just learning java and can't see the problem clearly >> enough to fix it. >> >> The question is: should I just ignore it and try to use eyeball? >> > > Yes. > > In fact, you shouldn't need to compile Eyeball at all - isn't there a > supplied jar file in the lib/ directory of the download? > > Andy > > >> >> Thanks in advance! >> >> >
