Try to create a small reproducible suite with this problem.
In theory what you did is correct and you don't have a duplicate of
commons-configuration but it's hard to debug this over email with partial info.
Also try looking at the actual build output JARs that you have, I'm not
entirely certai
Hi,
Yes that is what I think too.
I changed my architecture since I posted my issue.
I still have the issue but I think the best is to explain the module hierarchy :
- I have module A (netbeans module)
- the module A has a maven dependency to module B
- the module B has a dependency to a librar
