Conor MacNeill wrote: > > The reason this occurs under Gump is that Gump is not trusting. It > ignores the classpath provided by the build file in favour of its own > classpath. Gump, however doesn't have the necessarys jars in its > classpath because they have only just been built in the earlier stages > of the build.
Accurate description. See http://jakarta.apache.org/gump/why.html#2000 for my rendition. > So in the following build, the classes in antcore cannot see the classes > built in common even though the build file provides these in a compile > classpath. > > Is there any way around this problem? One way is to use http://jakarta.apache.org/gump/project.html#work thus: http://cvs.apache.org/viewcvs/jakarta-alexandria/proposal/gump/project/jakarta-ant.xml.diff?r1=1.29&r2=1.30 It even appears to work: http://gump.covalent.net/log/jakarta-ant-mutant.html - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
