Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Slide/jms dependency
Date: Tue, 13 Jan 2004 12:16:54 +0100
Message-ID: <84F0A43A4248CE45B5C0E20F4C40779C600AE2@naomi.webworks.nl>
Thread-Topic: Slide/jms dependency
Thread-Index: AcPZw4VsZquf3fmbRBiMTtaySXZ6EgAAqG3A
From: "Unico Hommes" <Unico@hippo.nl>
To: <dev@cocoon.apache.org>


Aw shoot, please ignore this. It seems that depending on a block *does*
add its dependencies to the classpath. The reason I didn't see it was
that the target I was running didn't recreate blocks-build.xml. Sorry
for the noise.

Unico

> -----Original Message-----
> From: Unico Hommes=20
> Sent: dinsdag 13 januari 2004 11:54
> To: dev@cocoon.apache.org
> Subject: Slide/jms dependency
>=20
>=20
> I am looking into adding a class to the Slide block that=20
> sends invalidation events over JMS so that the event caching=20
> system can pick them up and do its work accordingly. However,=20
> I am running into the problem that the class depends on the=20
> jms jar that is in the jms block.=20
>=20
> I tried adding a dependency on the jms block in gump.xml but=20
> that doesn't seem to work. Should there be a way declare a=20
> dependency on another block so that all of *its* dependencies=20
> are traversed and added to the compilation classpath as well?=20
> The other solution is to have a copy of the same jar in the=20
> Slide block too.
>=20
> WDOT?
>=20
> Unico
>=20
>=20