Anthony, I think what you're trying to figure out is out to parse the output file that is created while building with Ant. Are you using -logfile and -verbose flags for your log file? I haven't quite mastered parsing this log file myself either. Any success or ideas, please let me know, because I am interested as well.
-Nese -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, January 26, 2001 3:10 PM To: [EMAIL PROTECTED] Subject: Re: Adding output Thanks for the input Nico, but I think I might need to clarify a little bit. I am looking for the files ant is going to build. It has to know this. If it didn't know which files it was going to build, how would it work? It seems to me that ant is doing something completely different from what I am trying to do, so it looks like I'll have to parse the files manually, and run through all of the files I find that match the build file. Anthony Levensalor > ----- Original Message ----- > From: <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, January 26, 2001 8:23 PM > Subject: Re: Adding output > > > > I am trying to put together a helper utility that will > > parse a build.xml file and display the following things > > to the user: > > > > 1.) Complete classpath necessary for the build > > Where would you like to take this information from? Ant doesn't know this, > it's not included in the buildfile, ..? Even if you know what classes are > required to build, you still don't know where on the system these classes > are if they are not included in the classpath. Maybe the required jarfile is > not even available on the system? Where will you start searching and where > do you stop? > > > 2.) A list of all .java, .jar, .zip, etc. files that > > are used in the build. > > "That are used"? Do you mean are needed to compile? Isn't this the same as > 1)? > > > 3.) A listing of all of the classes that will be built. > > This information is not included in the buildfile and not available to ant. > > Maybe you can use the depend-task to do something like this, but I can't > tell you how. I think the classes included with the depend-task could be > capable of detecting the required classes and the classes which would be > generated (inner classes and non-public classes in the files, etc.). > > Conclusion: Don't know how you will get the required information form a > buildfile, so I can't really help you. > > Nico > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
