with 1.0 out, I think now is the time to get fortress into an organisational (ie no code changes) structure more similar to merlin and phoenix. I'm kinda expecting growth :D
How about....
----
1) breaking fortress out of excalibur.
At a minimum, that means making
http://avalon.apache.org/fortress/
work. Going a little further I would like fortress to break out of excalibur, making excalibur more about fortress and making fortress more findable. I like to think of fortress as Avalon-Fortress, not Avalon-Excalibur-Fortress. It could go into two places:
1a) ~/cvs/avalon/fortress
1b) ~/cvs/avalon-fortresswe talked (I think even voted) about 1a) before. IMHO it's preferable, but 1b) is workable, too. The latter might make it easier for people to use cvs branching as partial branching is not needed. 1a) will additionally require framework to move to ~/cvs/avalon/framework/.
2) splitting fortress up.
At a minimum, that means an 'api/' directory and an 'impl/' directory, and a fortress-api.jar and a fortress-impl.jar. However, I would like to restructure a little more rigorously, somewhat like merlin, with seperate subbuilds:
container/ # this is most of the current codebase
src/api
src/impl
src/test
platform/ # a Kernel 'n stuff
src/api
src/impl
src/test
tools/ # the meta tool and stoof
src/java
src/test
cli/ # the frontend Berin keeps talking
# about :D
src/java
src/test
servlet/
src/java
src/test
examples/
src/java
src/test
docs/
src/xdocs maven.xml # reactor build ensuring you can still build just as
project.xml # easiliy(note: not everything mentioned above even exists yet. But my hunch is that it will sometime soon.)
3) converting the build to maven.
A structure like the above would require rather a lot of work if it were to be done using ant, whereas using maven it is quite feasible. I would like to just switch over to maven in one go. This will in addition require little build.xml files to be written that will enable gump integration. More importantly, it will require y'all to install, and get to basic grips with, maven.
----
....you might imagine restructuring like this will take some time. I would like to get started with setting up the structure like this, then move over the actual sources later in one go. That should avoid disrupting the regular work.
thoughts?
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
