Closed hohwille closed 8 years ago
I am still trying to isolate the bug. What I figured out is that it only happens if I run the multimodule build via reactor. If I build the WAR by just calling it one the according module itself then the error does not occur.
The issue is gone in latest release build from git. IMHO this was caused by a side-effect that has been fixed with PR #13. Unfortunately I could not isolate a reproduceable IT but I have to complex projects where the error occurrs with beta-4/5 and goes away with the latest plugin.
In some more complex scenarios with depdencies using depdencyManagement via BOMs (e.g. from spring boot) I discovered that activating flatten-maven-plugin causes wrong version numbers to be calculated. One OSS example is oasp/oasp4j#140 and I found more cases even with the most recent version of flatten-maven-plugin. I am still trying to build a minimum isolated project reproducing the bug.
Further I assume that we need to revisit
createEffectivePom
method and see how we need to configuremodelBuilder
properly or if we need to replace it with a totally different approach.