Apply only over active profiles

[flabodotes]

When the property embedBuildProfileDependencies = true all the dependencies defined in the profiles are moved to project general dependencies. If you have the same dependency in several profiles but maybe with other versions after the flatten process the result contains duplicated definitions.

With the change proposed only the active profiles will be taken into account.

[hohwille]

Sorry, for the late response - I was totally under water with lots of other OSS and closed projects. Thanks for your PR. I see your point and agree that adding duplicated dependencies is to be considered as a bug.
However, the feature embedBuildProfileDependencies = true was introduced with a specific use-case in mind and is already used. Your PR will break the behavior of that feature in an incompatible manner. Therefore I can not accept your PR as is. We can discuss about introducing a new property to get the feature you are intending. However, this can easily result in different build-results depending on your environment what is actually an anti-goal for the initial idea of the project. Anyhow, I am not someone who wants to be a blocker of useful features for filling gaps in the maven ecosystem as I wrote this plugin exactly for the purpose of such gaps and because of my resulting frustration.
However, it would be very helpful if you could describe your use-case or intentions before we proceed. If it is just to avoid duplicate dependencies then we should file and fix an according bug (I will do that anyhow in the future, but I first want to verify this with an IT to get sure it really is as you tell).

[matthiasbalke]

@hohwille If this PR is breaking the API how about, increasing the major version and provide an upgrade tutorial?

[hohwille]

If this PR is breaking the API how about, increasing the major version and provide an upgrade tutorial?

There are always different users with different use-cases and requirements. What seems like a natural thing for you to have as default is considered sick for others.
Can you still write a few lines to describe your use-case (what you have in your pom and what you would expect of flatten plugin to do for you what is currently not possible)?