I can see two options: retire it from the docs, or set up a special doc area with lots of warnings on it for "unmaintained/experimental/use-at-your-own-risk/no releases" stuff.
We've talked about what to do with non-core stuff before, but this seems a bit different... ajs6f > On May 11, 2018, at 8:11 AM, Andy Seaborne <a...@apache.org> wrote: > > Edward found Eyeball via: > > https://jena.apache.org/documentation/tools/eyeball-getting-started.html > > Eyeball is mentioned: > > documentation/tools/index.mdtext > documentation/tools/eyeball-guide.mdtext > documentation/tools/eyeball-getting-started.mdtext > documentation/tools/eyeball-manual.mdtext > > The tools page has schemagen and eyeball on it. > > eyeball-getting-started says "file a JIRA". > > What should we do? > If it is not released, do we retire it from the documentation? > > Andy > > > On 04/05/18 11:39, Edward (JIRA) wrote: >> Edward created JENA-1541: >> ---------------------------- >> Summary: Jena Eyeball - ant test fails with TestCase Error >> Key: JENA-1541 >> URL: https://issues.apache.org/jira/browse/JENA-1541 >> Project: Apache Jena >> Issue Type: Question >> Components: Eyeball, Jena >> Reporter: Edward >> Hello, >> I'm trying to get Jena Eyeball running. I wanted to do the Tutorial on >> [here|[https://jena.apache.org/documentation/tools/eyeball-getting-started.html],] >> but it failed with following error: >> {code:java} >> [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] >> BUILD FAILED >> /**/Downloads/eyeball-2.3/build.xml:146: Test >> com.hp.hpl.jena.eyeball.inspectors.test.TestMoreOwlSyntaxInspector failed >> {code} >> The tutorial says if the ant test doesn't pass, I should file a Jira Issue. >> So that's what I am doing. >> Help would be much appreciated! >> Greetings, >> Edward >> -- >> This message was sent by Atlassian JIRA >> (v7.6.3#76005)
