https://bz.apache.org/bugzilla/show_bug.cgi?id=65183
Bug ID: 65183
Summary: Dependency on batik-all causes JPMS errors with OOXML
artifact
Product: POI
Version: 5.0.x-dev
Hardware: PC
OS: Mac OS X 10.1
Status: NEW
Severity: normal
Priority: P2
Component: XWPF
Assignee: dev@poi.apache.org
Reporter: mar...@volkhart.com
Target Milestone: ---
Using a build of the 5.+ OOXML artifact in an application built with the Gradle
modularity plugin, build-time errors report "error: the unnamed module reads
package org.apache.batik.transcoder from both batik.transcoder and batik.all
"
Batik-all is a strange artifact. It's POM declares dependencies on all the
sub-JARs, but its JAR has all of the sub-jars repackaged. This results in two
JARs with the package "org.apache.batik.transcoder". And since Batik doesn't do
any module naming, a conflict occurs.
I think the right answer here is to change the POI OOXML POM to use more
specific Batik dependencies, not batik-all. The Ant build already specifies all
of the individual JARs and doesn't use batik-all, so it likely doesn't exhibit
this behavior.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
