[
https://issues.apache.org/jira/browse/UIMA-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-5345:
---------------------------------
Description:
Some dependencies in the uimaj project are scope compile, which would be better
as scope provided, to allow downstream projects that depend on this to **not**
have these dependencies added to their project.
Examples: the jar that is used only at compile time to supply annotations for
Findbugs; the jars that are used at compile time for the log4j logging impl
(the downstream depender may not be using log4j, and having these causes maybe
wrong slf4j selection of the logging back end).
When moving log4j things to provided, this also removes them from the test
classpath, which makes the tests that need log4j break. Fix this by
configuring the surefire plugin to add these dependencies back just for testing
(a hack, but I don't know of a better way).
was:
Some dependencies in the uimaj project are scope compile, which would be better
as scope provided, to allow downstream projects that depend on this to **not**
have these dependencies added to their project.
Examples: the jar that is used only at compile time to supply annotations for
Findbugs; the jars that are used at compile time for the log4j logging impl
(the downstream depender may not be using log4j, and having these causes maybe
wrong slf4j selection of the logging back end).
> uv3 consider moving some scope-compile to scope-provided
> --------------------------------------------------------
>
> Key: UIMA-5345
> URL: https://issues.apache.org/jira/browse/UIMA-5345
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDK-alpha02
>
>
> Some dependencies in the uimaj project are scope compile, which would be
> better as scope provided, to allow downstream projects that depend on this to
> **not** have these dependencies added to their project.
> Examples: the jar that is used only at compile time to supply annotations for
> Findbugs; the jars that are used at compile time for the log4j logging impl
> (the downstream depender may not be using log4j, and having these causes
> maybe wrong slf4j selection of the logging back end).
> When moving log4j things to provided, this also removes them from the test
> classpath, which makes the tests that need log4j break. Fix this by
> configuring the surefire plugin to add these dependencies back just for
> testing (a hack, but I don't know of a better way).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)