[ 
https://issues.apache.org/jira/browse/JENA-2253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17481275#comment-17481275
 ] 

Andy Seaborne commented on JENA-2253:
-------------------------------------

The test artifacts for jena-base, jena-core and jena-arq now have different 
modules names to the main artifacts ".test" was added. No other artifacts have 
usable test code for 3rd party systems.

That's all I can think of so in the absence of more information , marking this 
resolved and closed at the Jena 4.4.0 release.

Feel free to reopen if new information is available.


> Add module-info.java
> --------------------
>
>                 Key: JENA-2253
>                 URL: https://issues.apache.org/jira/browse/JENA-2253
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Jena
>    Affects Versions: Jena 4.3.2
>            Reporter: Svante Schubert
>            Priority: Trivial
>
> I am quite new to the Java 9 modularity,  but my developers told me that it 
> can be "enabled" by adding some basic module metadata in a 
> {{module-info.java}} at the root of the java sources.
> Therefore, I suggest adding a module-info to your Jena project, so that users 
> who are using a java module based project setup can benefit from this.
> We, the ODF Toolkit, are using Jena and we started such 
> {{{}module-info.java{}}}: 
> [https://github.com/tdf/odftoolkit/pull/149/files]
> But somehow as soon we got this metadata the Java classes of the 
> jena-core-tests JAR can no longer be found.
> The tests are not in our package list as we use them just during build/test 
> time.
> Perhaps I can make one of you curious enough to test to create such simple 
> {{module-info.java}} files to the root of your Java sources similar as done 
> in the PR from us: [https://github.com/tdf/odftoolkit/pull/149]
> (The other reason for this issue, is also that we face an anomaly of lacking 
> to find your jena-core-tests classes after using this new module-info.java. I 
> hope that this phenomenon goes away when you add your module-info.java as 
> well. Currently, [accessing the jena-core-tests via pom.xml in the old 
> way,https://github.com/tdf/odftoolkit/blob/master/odfdom/pom.xml#L72] but the 
> [new way using apache-jena-libs in 
> pom.xml|https://jena.apache.org/download/maven.html does not work either.).
> Thanks in advance,
> Svante



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to