Hi,
Are you referring to the binary distro? AFAIK, the binary distro only
contains artifacts under modules and their compile/runtime dependencies.
I think it should be individiual sample's reponsiblity to declare extra
dependencies. These dependencies should not be included in the binary
distro.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, November 14, 2007 12:47 PM
Subject: Sample dependencies not pulled in distribution
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
