[
https://issues.apache.org/jira/browse/UIMA-3381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805596#comment-13805596
]
Marshall Schor commented on UIMA-3381:
--------------------------------------
This web page,
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html,
seems to address Richard's use case, and says that maven would include A via
the other path from X. The key phrase seems to be that when you do an
exclusions, "that artifact will not be added to your project's classpath by way
of the dependency **in which the exclusion was declared**. They then go on to
give an example which seems to follow the example Richard gives, and say that
having a dependency on A via another path, would include it (no mention of
"closest first").
I guess it might be good to actually test this :-)... Or, perhaps I've misread
this...
> Trim UIMA-AS dependencies
> --------------------------
>
> Key: UIMA-3381
> URL: https://issues.apache.org/jira/browse/UIMA-3381
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Fix For: 2.4.2AS
>
>
> The uimaj-as-activemq pom declares dependency on activemq-web which in turn
> has transitive dependencies on many other parts including hadoop,google
> guiice, jackson and others. This just bloats the classpath with unnecessary
> dependencies and forced downloads during maven builds.
> Modify poms to exclude transitive dependencies.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
