Geoffrey Wiseman wrote:
>
> parent (pom, multi-module; any common dependencies or dependency
> management,
> plugin management, etc.)
> - common (common source code; jar)
> - dev1 (depends on common; adds config; can overlay/flatten/shade jar if
> you
> like)
> - dev2 (same as dev1, but with its own config)
>
> Each of common, dev1 and dev2 would have their own pom, and be modules
> under
> the parent build.
>
Hi Geoffrey,
dev1 has a jar packaging type?
Because in that case I get an almost empty jar, but I need the classes
generated in the common.
Thanks
Czollli
--
View this message in context:
http://www.nabble.com/Multimodule%2C-multilevel-project-tp21806770p21827159.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
