#5 Java warnings

[Paul Newport]

Code contains many warnings when imported into
Eclipse (typically unused imports).

These are easily fixed by using Organize Imports in
Eclipse (CTRIL SHIFT O).

Also it would be better if all the classes weren't in the
one, default, package.

[Morgan Schweers]

Logged In: YES
user_id=19745

Greetings,
G0d, I wish I hadn't put it all in one mondo-package to begin with.

The nightmare here is that I *can't* change it now, because of the
limitations of CVS. I lose my entire source history if I try to migrate to a
new directory structure.

I've spent time fixing up a lot of the unused import stuff, I thought I'd
gotten it mostly weeded out. I haven't tried using Eclipse to import, but
running a few other tools like PMD on it found a few similar things as I
recall.

Sorry about the mondo-package. I could reorganize, but because Java is
VERY dependant on the directory structure matching the package
structure, and CVS doesn't allow restructuring the directory structure, I'm
afraid the package problem is hosed.

Some day, when I go 1.0, I might start a new project within the
JBidwatcher project, start with a clean slate, migrate all my source to
the right spots in the new tree, and work from there, but right now I'm
afraid we'll have to live with the bad layout.

-- Morgan Schweers, CyberFOX!

[Paul Newport]

Logged In: YES
user_id=988075

Hi

Using Eclipse you can refactor to your hearts content and
then synchronise with CVS. It isn't a problem. YOu should be
able to refactor the whole thing in about 10 minutes,
assuming you know which packages are going where.