You are viewing a plain text version of this content. The canonical link for it is here.
Posted to odf-dev@incubator.apache.org by "Olivier Cailloux (JIRA)" <ji...@apache.org> on 2017/08/17 11:26:00 UTC

[jira] [Created] (ODFTOOLKIT-464) Pom does not follow best practices: missing optional keyword

Olivier Cailloux created ODFTOOLKIT-464:
-------------------------------------------

             Summary: Pom does not follow best practices: missing optional keyword
                 Key: ODFTOOLKIT-464
                 URL: https://issues.apache.org/jira/browse/ODFTOOLKIT-464
             Project: ODF Toolkit
          Issue Type: Bug
          Components: simple api
            Reporter: Olivier Cailloux
            Priority: Minor


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 https://repo1.maven.org/maven2/org/apache/odftoolkit/taglets/0.8.11-incubating/taglets-0.8.11-incubating.pom). Similarly, org.slf4j:slf4j-log4j12 is passed on 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 https://stackoverflow.com/questions/32231814/how-can-i-remove-logback-from-a-librarys-dependency-while-keeping-slf4j .)

Workaround: add exclusion rules for these artifacts (see https://github.com/oliviercailloux/Test-ODFToolkit-ODS/blob/master/pom.xml).

(I tried to discuss it [here|https://lists.apache.org/thread.html/6fa4257e67ede90bac58f5518e1be41e7561a451149cbc9eecdbbf1e@%3Codf-users.incubator.apache.org%3E] but received no answer.)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)