Though technically excellent, the dependency checking system is not
something I particularly like.
When I see such dependency, I usually question if the separation in packages
was done well afterall.
IMH(and very personal)O, a jar package from a software module must not have
complex dependencies with another jar package from the same module.
Dependencies should be usually inter-module, not intra-module.
This keeps things cleaner and more manageable.
What's the use of having different dirs, when you still have to build the
code "together"?
It's like recreating by hand something that javac does automatically.
In the spirit of KISS, what I would like to see is a more clear
stratification of excalibur packages: groups of packages are build one on
top of the other. So there would be
excalibur-foundation (basic _excalibur_ framework)
excalibur-dungeons (excalibur utils)
excalibur-castle (excalibur proper)
excalibur-tower (excalibur avvanced features)
Each group is compiled before the other, in a simple and clean manner.
This doesn't mean that you should change the dirs again... it's just the
build.
Packages are assigned to a group and compile that way; there would be only 4
jars, but with a dependency that is much easier to resolve for the excalibur
user.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
