🚀 go-pugleaf

Mikael Fransson <mikael.fransson@aspiro.com> wrote:
> I think you missed my point...

> I'm going to write a class tester for JUnit where the only thing I have is a
> package name
> and I know that there are a lot of classes with only setters and getters and
> ofcorse a constructor.

> I have finished the test code for all the setters and getters but now I need
> some thing to collect the classes for me.
> its not necessary that I get them as Class, if I get the names I can create
> the Class object my self.


Didn't someone already just announce this support for JUnit?  I know there is
one that works based on a specified source tree of tests.

Keep in mind that when you're querying the JVM, you're seeing only the classes
which the JVM itself has loaded.  You aren't seeing everything that possibly
exists out in the CLASSPATH but which hasn't been used.

Anyway, what you need to do is loop through the CLASSPATH looking for
directories and jars which contain that package name.  You have to look at the
disk for directories, and open the jar files yourself.  Once you find the package
in something, read in its contents.  You have to do this for every item in the
CLASSPATH because a package can exist in multiple jars and/or directories.

-- 
Joi Ellis (TeamB) 
No direct email, please.
For best results, post on news server newsgroups.borland.com!
Newsgroup Info: http://www.borland.com/newsgroups/guide.html