[
https://jira.codehaus.org/browse/MASSEMBLY-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340871#comment-340871
]
Andrew Logvinov commented on MASSEMBLY-594:
-------------------------------------------
Personally I don't use dependencyManagement at all, since I find it quite
useless. If two or more modules depend on the same library (for example,
log4j), I move it to parent pom that all of the children inherit from. If I
used dependencyManagement, I'd have to define the log4j version in parent pom,
and then explicitly add it to set of dependencies in each of the chlid
projects, which is a lot of copy-paste.
But I agree that this issue seems to have been fixed. It is reproducible with
2.3 version of assembly plugin, but no longer reproducible with 2.4 version.
> Add ability to suppress "already added, skipping" messages
> ----------------------------------------------------------
>
> Key: MASSEMBLY-594
> URL: https://jira.codehaus.org/browse/MASSEMBLY-594
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Reporter: Andrew Logvinov
>
> A common multi-module project structure would define most of the project
> dependencies in the parent POM thus allowing all the child modules to inherit
> them. When packaging all the project dependencies using <moduleSet>, you'd
> see a lot of messages like this (and in case of big project the number is
> huge):
> {noformat}
> [INFO] lib/log4j-1.2.15.jar already added, skipping
> [INFO] lib/mail-1.4.jar already added, skipping
> [INFO] lib/jms-1.1.jar already added, skipping
> {noformat}
> It would be great to either have an option to suppress such info messages, or
> to have them moved to DEBUG log level.
> See example of configuration here:
> http://stackoverflow.com/questions/4912738/maven-assembly-include-all-sub-module-dependencies-without-already-added-skipp
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
