Hello, I have library A that depends on B (A -> B) and I thought of making separate library wrappers for both.
So module X wraps A and makes everything public while module Y wraps B and X depends on Y (X -> Y). Seems to me nbm-maven-plugin will add all the transitive dependencies in the classpath (in the ext/) and disregards the cross-library wrappers dependency. I end up having B in X *and* Y. Of course, I can exclude that manually but it's finicky. Anybody else encountered something like this? I suspect I might have to patch nbm-maven-plugin but I'd rather avoid jumping into that too. --emi
