Hi,
I was about to clarify a bit. What I meant is the extra dependencies
required by a sample should only go into the sample structure instead of
polluting the lib folder. It's a bit challenging to have a good balance: on
one hand, we don't want to create a monster distro as samples can bring in
extra dependencies; but on the other hand, it would be simple to package
everything in.
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Wednesday, November 14, 2007 1:20 PM
Subject: Re: Sample dependencies not pulled in distribution
Raymond Feng wrote:
Hi,
Are you referring to the binary distro?
Yes
AFAIK, the binary distro only contains artifacts under modules and their
compile/runtime dependencies.
Correct
I think it should be individiual sample's reponsiblity to declare extra
dependencies.
Yes, makes sense. It does actually.
These dependencies should not be included in the binary distro.
With my user hat on, how do I run a sample that needs derby, am I going to
have to go download derby by hand, put it on my classpath etc?
Shouldn't whatever distro includes the binary samples include their
dependencies as well?
--
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]
