[ODFTOOLKIT-464] Pom does not follow best practices

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Component/s: simple api
• Assignee: Svante Schubert
• Reporter: Olivier Cailloux
• Created: 17/Aug/17 11:25
• Updated: 19/Sep/17 18:32
• Resolved: 19/Sep/17 10:04

Description

When depending on Apache ODFToolkit simple-odf in my application (org.apache.odftoolkit:simple-odf:0.8.2-incubating), I observe that com.sun:tools is transitively imposed on my project as a dependency (coming from taglets, see its POM, coming from org.apache.odftoolkit:odfdom-java:0.8.11-incubating). Similarly, org.slf4j:slf4j-log4j12 is passed to my project as a dependency.

I suspect these dependencies are actually not required for projects depending on simple-odf.

It is possible and simple to ease the life of users of simple-odf by adding <optional> in the relevant pom files. This would respect Maven best practices. (See for example SO.)

Workaround: add exclusion rules for these artifacts (see this example POM).

(I tried to discuss it here but received no answer.)