Christian Goetze wrote:
I have a situation where a module with packaging "jar" builds, i.e. it
produces a .jar file, but it doesn't install if maven is run from the
parent project directory. No indication by mvn why. It will install if
I run maven from the module directory.
By removing all modules and adding them back in one by one, I discovered
that as soon as I add in a module with an assembly, subsequently built
modules do not get installed. This looks like a bug to me.
My workaround is to add dummy dependencies with <scope>provided</scope>
to force the reactor to execute builds in an order where the modules
with assemblies are built last. This will of course only work as long as
the modules with the assemblies remain leaves in the dependency tree...
Comments?
--
cg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
