Re: Building on Fortress

[Leo Simons]

J Aaron Farr wrote:

Hello.

I've been working on a Fortress based project lately but I'm having some issue
keeping my code base up to date.  So far I've gathered that:

1. There's an excalibur-fortress-1.0.jar floating around (I know it's in
Maven's ibiblio repository, but I think it's elsewhere) but it's not recent.

that jar is not really ment for actual usage; don't know where it came from. Regardless of the name, it isn't actually a 1.0 release.

2. I've pulled the fortress code from CVS, but it seems as if this can't be
built against avalon-framework 4.1.3.  (If I'm wrong here, please let me know).

I'll check asap. The goal is definately to get it to build against that!

3. So if I want the latest Fortress I should either pull everything from CVS
(including the framework) and build from there or see what I can pull from the
GUMP nightly builds.  Does that sound like a sane approach?

does to me, it does. You probably want to run on cvs until we release, as the cvs version will grow ever closer to the release version.

I know there's been talk about getting a release of Fortress out soon, and I'm
wondering what still needs done.

besides the stuff Steve already mentioned, we're aiming for an across-the-board release where we release lots of avalon materials which have been tested to work together.

I've tried reading over the dev mailing list
archives, but I'm not sure what the status is.  Is there anything that a lowly
user might be able to do to get Fortress out (docs, patches, testing...)?

all of the above! Some docs stuff that would be nice:
- javadocs. You can easily find dozens of class members or even whole classes without docs
- an actual hands-down user guide which talks one through the existing examples (I'm wanting to rip stuff out of the tweety quick start guide)
- update of "Developing with Avalon" for fortress
- migration guide for ECM users

code stuff:
- more and more sensible debug logging output
- we need to look at exception handling
- i18n (using the excalibur i18n package of course :)
- inline code comments to clear some things up
- checking code for any hard-coded parameters and make them less hardcoded
- unit tests. Loads and loads of classes don't have 'em

testing:
- always welcome! Since you're actually building an app, what issues have you run into? What did you like? What not?

this holds not just for fortress, but for all packages it depends on as well, like event. In short, there's loads of stuff you can do, with varying degrees of difficulty :D

cheers,

- Leo



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>