Jörg Schaible wrote:
Hi folks,
after some hours testing M206 and looking for solutions, I am quite helpless
with our build that is broken if I run a multi-project build. Part of this
build is the creation of an ejb-client jar and another artifact that is
dependend on it. Unfortunately the dependent artifact cannot be compiled,
because the classes from the ejb-client are misssing.
Culprit seems to be indicated by the line from the resources:resources goal, where the
ejb-client is listed with a scope of "null":
[DEBUG] ip.evtmon:ip-evtmon-ejb:ejb-client:client:2.2.2-SNAPSHOT (selected
for null)
and therefore it seems consequently omitted compiling the classes, since it is not part of the
classpath anymore. If I build the module locally there's no problem, the scope is
"compile", but not when running in a multi-project build. I already tried to introduce a
dependencyManagment section in the local POM where I declare this artifacts again with explicit
scope "compile". Any idea what might cause this?
- Jörg
Hi - I expirience the same - but only when running a multiproject:
parent
-ejb-project (generating ejb and ejb-client)
-client-project (using ejb-client)
If I try a multibuild it fails, if I cd into client-project and do mvn
clean install it succeeds.
--
David J. M. Karlsen - +47 90 68 22 43
http://www.davidkarlsen.com
http://mp3.davidkarlsen.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
