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