Hi Mike.
I understand why jorphan exists as it is, and it makes sense to me --
it's the kind of stuff that people will keep reinventing until it's
somehow added to a Standard Java API.
However, I didn't feel confortable with binaries (compilable from the
project sources) existing in CVS. It has actually caused me some damage
in the past, when I was trusting ./build.sh would do a clean rebuild and
it wasn't the case.
I'm now in the process of doing the changes necessary to make the
different sections (jorphan, core, etc.) as independent as possible (as
we talked a few weeks ago). Once this is done, I'll also make sure
jorphan.lib and all other source-obtainable stuff (e.g. docs) is cleaned
up before a clean build.
Makes sense?
Salut,
Jordi.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
- RESOLVED bugs Jordi Salvat i Alabart
- Re: RESOLVED bugs Mike Stover
- Re: jorphan [Was: RESOLVED bugs] Jordi Salvat i Alabart
- Re: jorphan [Was: RESOLVED bugs] Mike Stover
