Kevin, I wasn't 100% clear on whether you were addressing me (Matt Lyon) or Matt McCauliffe, who originally spawned the thread. However, assuming you were asking me, I didn't bother reverting to Ant 1.4.1 sans environment variables as a test case once we had a solution in place to move forward with Ant 1.5 plus environment variables. If I find some cycles today I can try to diff the ejbc calls in the Ant 1.5 code base against the same in Ant 1.4.1 and post any meaningful insights I happen to derive.
Cheers, Matt -----Original Message----- From: Duffey, Kevin [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 10:42 AM To: Ant Users List Subject: RE: ebjc errors Hey Matt, You guys tried going back to 1.4.1 and see if it fixed the problem? Not always the case, but if it works on 1.4.1, and not on 1.5, then either Ant is the problem (not likely), or something Ant is doing when invoking ejbc is different. You could check the src of both versions and see if anything changed. -----Original Message----- From: Matt Lyon [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 7:13 AM To: Ant Users List Subject: RE: ebjc errors FWIW, We ran into this on one of the developers' systems in our shop under the Ant 1.5 upgrade. I didn't get down in the weeds to find out the exact why's, but found that setting %ANT_HOME% to the root install of ant (e.g. C:\ant or some such), setting %JAVA_HOME% to the root dir of the jdk install (e.g. C:\jdk131 or whatever), and then adding %ANT_HOME%\bin and %JAVA_HOME%\bin to the %PATH% fixed the problem. I'm not sure why Ant 1.4.1 was working without the definition of these environment variables, I haven't diffed the scripts shipped with the Ant binary distros of 1.4.1 and 1.5. HTH, Matt -----Original Message----- From: Conor MacNeill [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 24, 2002 8:09 AM To: Ant Users List Subject: Re: ebjc errors Eddie Bernard wrote: > Conor- > > I'll help out on this, since Matt and I are both working on the same > problem. > > Under previous versions of Ant, we did not encounter this problem. However, > I'm not sure that this is in fact an Ant problem. We're thinking that it > may be a Windoze problem of running out of command line buffer. What's > perplexing us is that this problem just manifested itself recently and has > not been a problem in the past. We also have other build systems that > construct much larger command lines and works fine. We've also found that > we can replicate the problem only under unique circumstances and it's not > always consistent. > Hmmm, odd. If you can replicate it I would suggest running with the -debug flag to see what command line is being used. If you can cut and paste that onto a command line (you may need to use keepgeneric for that) and see if it works from there. As you can see the error is actually occuring in ejbc, not ejbjar - so technically not part of Ant. It would be interesting to contrast the command line with 1.4 in this case. > We're going to try and run this using MKS and CygWin to see if it errors out > the same way. I don't think either of these will have an impact since they are not involved when Ant invokes java to run ejbc, but worth trying anyway. Conor -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
