I think that all you need to do is to put in the classpath that you use in your <available/> task invocation all the jars needed, that is the ones containing the class itself, the ones containing the parents of the class, and containing the fields. Parent classes and fields can bring in extra dependencies. Maybe this is what happens.
Regards, Antoine -------- Original-Nachricht -------- Datum: Tue, 7 Nov 2006 11:59:39 -0800 Von: "Chun Ji" <[EMAIL PROTECTED]> An: "Ant Users List" <user@ant.apache.org> Betreff: RE: Ant "available" task > Hi Antoine, > Thank you for the tips. > For your second case, what happen if a parent class is located in a jar > file, would that be possible for this "available" task to check the child > class ? > > What I have found is for such scenario, of the same classpath setting, if > I was to check the availability of the parent class, it would load the > parent class from the jar file, and set my "present" property to be true. > > But if I was to check the availability of the child class, it gives me > errors as " Could not load dependent class ... , Unable to load child class to > set property ..."? I have a feeling once it finds the child class, it > never check the other files for the parent class. > > > -cji > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
