That is true within Maven/Surefire. Within Eclipse it should however work.

I don't think it is an important thing to test - or possibly even a feature
we need. It might be better to remove the static {} block in JenaJSONLD?

(Note that Andy's original code had a static {}  block which did the real
work, and an init() that did nothing. This avoided a call to
JenaJSONLD.init() to do double-initialization - but it means you can't do
re-initialization, such as after calling the Jena registry reset methods
(which I do somewhere else in my code).



On Wed, Oct 2, 2013 at 12:11 AM, Peter Ansell <notifications@github.com>wrote:

> In
> integration/jena/src/test/java/com/github/jsonldjava/jena/JenaRiotReadWriteTest.java:
>
> > +import com.hp.hpl.jena.rdf.model.Model;
> > +import com.hp.hpl.jena.rdf.model.ModelFactory;
> > +import com.hp.hpl.jena.sparql.lib.DatasetLib;
> > +import com.hp.hpl.jena.sparql.sse.SSE;
> > +
> > +/** tests : JSONLD->RDF ; JSONLD->RDF->JSONLD */
> > +public class JenaRiotReadWriteTest {
> > +
> > +
> > +    @BeforeClass
> > +    public static void init() {
> > +        /*
> > +         * Disabled to test that static { } in JenaJSONLD forces init() by
> > +         * accessing the field JenaJSONLD.JSONLD.
> > +         */
> > +        //         JenaJSONLD.init();
>
> Is this is a manual test?
>
> As far as I know, by default surefire will run all tests in the same JVM,
> so it depends on the order of the test classes at runtime (which is
> unpredictable as far as I know, you can only do intra-class method ordering
> as far as I know) as to whether this would actually be the first test
> (given that the other tests will already be triggering it automatically or
> manually in the test class.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/jsonld-java/jsonld-java/pull/71/files#r6702800>
> .
>



-- 
Stian Soiland-Reyes
Manchester, UK
http://soiland-reyes.com/