-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 13 Jan 2006, Reinhard Poetz wrote:
Date: Fri, 13 Jan 2006 21:56:10 +0100
From: Reinhard Poetz <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
Subject: Re: Block deployment: working with blocks from a user's point of view
Giacomo Pati schrieb:
> I've missed to place the dependant jars of a block. So I propose they go
> to META-INF/lib with no strong agruments for it but they are needed to
> setup the classloader for the block or to populate the parent
> classloader and that's done at initialization time.
>
> WDYT?
IMO we shouldn't add the jar files, that our blocks depend on, to our blocks
but put them into WEB-INF/lib for now. My plan is using M2 dependency
resolving that enables us to ask for all dependencies of a group of jars (see
my experiments in the deployer-maven-plugin). This way M2 takes care that we
only install one jar in one version.
Yes, correct. We do have M2 to solve them for us.
When our blocks become OSGi bundles, this problem gets automatically solved.
- --
Giacomo Pati
Otego AG, Switzerland - http://www.otego.com
Orixo, the XML business alliance - http://www.orixo.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDyCLxLNdJvZjjVZARAhrzAJ9KQGG7rDmniV3fsS8vQeU3MzmXbACg8HR5
1KFqrjPEHj8blub2aYOhMbg=
=/ddR
-----END PGP SIGNATURE-----
