🚀 go-pugleaf

I believe that this could be a bug in the dependency checker. Dependency
information is created on a package by package basis. When the same package
appears in two (or more) separte jars, the dependency checker finds the
dependency file for the first jar on the classpath, and assumes that it
contains information for all the classes in that package. This causes the
compiler to not be able to loacte any classes for that package that only
appear in the second jar. By switching the order of the  jars, you switch
the list of visible classes. A workaround is to find the package that is
split accross two jars and place them all of its classes in one jar or the
other, and delete its dependency files. The next time the compiler needs the
dependency information, it will generate an accurate one from scratch.

Andrew Fellows wrote:

> Having just completed a component for a project I was suprised to find
> that it wouldn't compile in the JBuilder IDE ... after checking the
> project properties and seeing the libraries pointed to the right place I
> was eventually reduced to changing the order in which the libraries
> appear in the list ......results :
>
> If JCL is before Swing .... errors
> If Swing before JCL ........ no errors
>
> The error in question is about CellRenderer ...... but this isn't the
> real problem as far as I can see... the real problem is why should the
> order of the libraries make a difference ??... all the classes belong to
> various packages so no name space clash should be happening ..... it's
> very frustrating to have something working with the vanilla JDK/Swing
> and not working in JBuilder even though ( so the property panel tells me
> ) it's using the same libraries ....
>
> Any ideas are appreciated , please CC it to my email
>
> Thanks
>
> Andrew Fellows
> Software Developer
> Sydac