Mavenizing dependencies which are part of another (sister) module

[a-zink]

Given following module structure:

• base
  • base-core
    • de.visualrulespatch.velocity.tools
  • base-java
    • de.visualrules.codegenerator.m2m

while "m2m" plugin depends on "velocity-tools" plugin and the mavenizor configuration only lists the "m2m" plugin as "inputBundle". Also there is no other plugin in the base-core module which depends on the "velocity.tools" plugin.

When building the base-java module it can now happen that the "velocity-tools" plugin only gets partially deployed and the pom is missing.
The "velocity-tools" plugin has to be configured as "inputBundle" in the mavenizor configuration explicitely, otherwise the build should fail.