[
https://issues.apache.org/jira/browse/JENA-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861996#comment-16861996
]
Andy Seaborne commented on JENA-1720:
-------------------------------------
jena-base also depends on commons-io:2.6 as does
com.github.jsonld-java:jsonld-java:jar:0.12.3.
apache-jena-libs:pom:3.12.0 works (see below).
Taking Erich's POM file, without common-io dependency and running {{mvn
dependency:tree}} I get:
{noformat}
[INFO] com.ebremer:ImageBox:jar:1.1.0
[INFO] +- org.apache.jena:apache-jena:pom:3.12.0:compile
... no commons-io ...
[INFO] +- ome:formats-gpl:jar:6.1.1:compile
[INFO] | +- org.openmicroscopy:ome-common:jar:6.0.3:compile
...
[INFO] | | +- commons-lang:commons-lang:jar:2.4:compile
[INFO] | | \- commons-io:commons-io:jar:1.4:compile
{noformat}
so it looks like a dependency problem.
commons-io:commons-io:jar:1.4 does not have BOMInputStream
For a POM of just org.apache.jena:apache-jena-libs:pom: I get:
{noformat}
[INFO] +- org.apache.jena:apache-jena-libs:pom:3.12.0:compile
[INFO] | +- org.apache.jena:jena-tdb:jar:3.12.0:compile
[INFO] | | \- org.apache.jena:jena-arq:jar:3.12.0:compile
[INFO] | | | \- org.apache.jena:jena-base:jar:3.12.0:compile
... no commons-io ...
[INFO] | | +- com.github.jsonld-java:jsonld-java:jar:0.12.3:compile
[INFO] | | | \- commons-io:commons-io:jar:2.6:compile
...
{noformat}
Conclusion: not something org.apache.jena:apache-jena-libs:pom can do much
about.
> Apache commons-io needs to be added as dependency
> -------------------------------------------------
>
> Key: JENA-1720
> URL: https://issues.apache.org/jira/browse/JENA-1720
> Project: Apache Jena
> Issue Type: Bug
> Components: Jena
> Affects Versions: Jena 3.12.0
> Reporter: Erich Bremer
> Priority: Minor
>
> In using RDFDataMgr.write(out, m, RDFFormat.JSONLD_PRETTY)
> to write out a Model as jsonld, an error was generated for a missing library
> found in apache commons-io. Adding
> <dependency>
> <groupId>commons-io</groupId>
> <artifactId>commons-io</artifactId>
> <version>2.6</version>
> </dependency>
> to my maven project resolved the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
