Dependencies from our samples do not seem to be pulled in the distro,
unless a module under modules/ also has a runtime or compile dependency
on them.
For example if you build a distro containing the implementation-data
module (but not containing implementation-bpel which has a compile
dependency on derby), derby won't be pulled in the distro. We need derby
to run the samples that use implementation-data... without derby they'll
break.
Does anyone know how the distribution build currently determines the
dependencies packaged in the lib directory of the distro?
Thanks
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
