I would say the canonical way to satisfy the nbm pluign is to add the
gui-module->spring-ws-library-wrapper dependency. we probably could add the
rule to the nbm-plugin, but it would make it more unpredictable what is
going to happen.
In a way the gui-module-domain shall not depend on the library wrapper
itself but the actual spring-ws content (which is being pulled transitively)

just my 2 cents,

milos

On Mon, Nov 30, 2009 at 3:01 PM, Eric Malotaux <[email protected]> wrote:

> Hi Milos and others,
>
> I have a chain of dependencies like this:
>
> gui-module (nbm) -> gui-module-domain (jar) -> spring-ws-library-wrapper
> (nbm).
>
> When building the gui-module with maven and the nbm-maven-plugin, I get a
> "transitive dependency" warning about the spring-ws-library-wrapper nbm
> module.
>
> Is the above dependency chain legal? Or should I make all modules between
> the first nbm module and the last nbm module nbm modules also?
>
> --
> Eric Jan Malotaux
>

Reply via email to