Peter Palaga

A PR is welcome.

Please explain better (1) sum up the current behavior (2) what is wrong with the current behavior and (3) what is the expected behavior

Which goals are affected?

An integration test in https://github.com/mojohaus/license-maven-plugin/tree/master/src/it reproducing the issue would be highly welcome.

> It would be better if we could filter artifacts out during dependency resolution. I think that would be nice for performance reasons too. > `excludeTransitiveDependencies` always be `true` In...

A PR with an integration test is welcome.

Thanks for the test. A fix is welcome as well.

@nfalco79 describes a workaround in https://github.com/mojohaus/license-maven-plugin/pull/318#discussion_r275789310 : > Change the preparationGoals of the mave-release-plugin from it default value (clean verify) to clean install so that when the release plugin run...

Thanks for the report. Yes, I think adding CopyOption.REPLACE_EXISTING could fix it. Looks like we have just two integration tests with `organizeLicensesByDependencies=true` which apparently do not cover this situation. Please...

Looks like a valid use case. Feel free to submit a PR that would contain at least one integration test. P.S.: Windows CI works now and I am in the...