Re: ws-jaxme failure on Gump

2004-10-07 Thread Stefan Bodewig
On Wed, 6 Oct 2004, Adam R. B. Jack [EMAIL PROTECTED] wrote: The reason the we-jaxme descriptor has mkdir entries and work entries is that (perhaps historically) the JVM would drop system classpath parts that did not exist at Ant's start-up. Not historically, still does. It doesn't affect

ws-jaxme failure on Gump

2004-10-06 Thread Adam Jack
I took a look at the ws-jaxme configuration, and its Ant scripts. As far as I followed it, I was wrong about this being a simple work or depend problem. I wonder if it is a clean environment problem. Looking at the build output:

Re: ws-jaxme failure on Gump

2004-10-06 Thread Jochen Wiedmann
Hi, Adam, thanks for looking into this. Your diagnosis is mainly tight: The code generator (chainGenerator) ought to load the class AttributeSG in order to create a derived class. In the past, you had been completely right: The task required the *compiled* class AttributeSG. However, this is no

Re: ws-jaxme failure on Gump

2004-10-06 Thread Adam R. B. Jack
Jochen Wiedmann wrote: Considering this, and the strange things that Gump does with classpaths: Is it possible, that the directory ${src.jm} (aka src/jaxme) must be added to the project descriptor? Given that Gump enforces control over classpaths (with a little willing participation from Ant,