#1 Organize your Code with packages

You should move your source files into packages.

e.g.:

com.jbidwatch
com.jbidwatch.auction
com.jbidwatch.gui
com.jbidwatch.util

So it would be much easier to understand the code.

I tried it myself, but I had not enough time to get into
your code to seperate the dependencies.

[Morgan Schweers]

Logged In: YES
user_id=19745

Greetings,

At this point in time, the dependencies are too
intertwingled. I can make a com.jbidwatch package, under
which everything sits, but you can't break up the code right
now completely. A *lot* of people want to use the code as
just an API, and I even have code that uses it as such, but
it still requires the UI portions to be linked with it.
There's a dependency between AuctionsManager and some of the
UI code, which makes everything interdependant. I want to
break all those dependencies, but it's not a priority yet.
It's one of the 'major rearchitectures' for post-1.0.

-- Cyberfox

[Morgan Schweers]

Logged In: YES
user_id=19745

Greetings,
Actually, one of the problems is that packages require
subdirectories, and subdirectories require moving my files
around. Moving files around is very much NOT supported by
cvs, so my source history would go kaput.

Ick... I need to come up with a way to solve that, somehow.

-- Morgan

[Nicolas Schmid]

Logged In: YES
user_id=893530

hi there,

you postponed this bug for over 2 years now! isn't there any
for you acceptable way to do the packaging? i would do it
for you, but you have to come up with a solution for the cvs
problem. i would suggegst accepting to loose revision
history and completely remove the old structure (possibly
tagging it first).

greetings

nicolas schmid

[wa7son]

Logged In: YES
user_id=1251991

One way to move the file to a new location in CVS would be to:
1. Copy the file locally
2. Remove the old file from CVS
3. Add the new file to CVS

This way you would have version history on the project as a
whole, but not on the new file it self of cause (you would
have to know or add as a comment where the old file is located).

But I would argue that this way of doing it is better then
not having it in packages at all! - Hopefully there is no
greater need to go back and build older versions of the
software?

/watson

[Nobody/Anonymous]

Logged In: NO

for for your info guys: apparently JBW is now migrating over
to SubVersion, so the CVS limitations should no longer be a
factor anymore-thus, if you are still willing to get
involved, I'm sure your support would be appreciated!