Re: Annoying Java Class/Nib problem
Re: Annoying Java Class/Nib problem
- Subject: Re: Annoying Java Class/Nib problem
- From: "Doug Knowles \(PB\)" <email@hidden>
- Date: Thu, 12 Jul 2001 09:43:57 -0400
I was seeing a lot of errors like this when I first tried putting my
application class in a package (rather than leaving it package-less, as PB
does by default). Tweaking the project and application settings to get
classes qualified with package names to work can get a little finicky. (I
was even advised at one point to avoid doing it, if possible. It's probably
good advice, which I'm not following at my own risk because I'm using a lot
of pre-existing packaged Java code.)
Although I haven't confirmed this, I have a suspicion that PB leaves "old"
build products around under some circumstances; for example, if one excludes
a file from a build target (by clicking off the little circle indicator), or
changes the package designation. This might cause code to appear to work
for a while (because it's including the old code), but it's really not what
you want, and it makes it difficult to figure out what broke things when it
suddenly stops working.
I was re-creating project files on a regular basis for a while, but I
haven't had to recently. I do find it necessary to perform a "Clean" and
rebuild occasionally, and I do it now and then "just in case." In extreme
cases I manually clear out the build products directories, but I haven't
found it necessary for a while.
Doug K;
----- Original Message -----