We've mentioned the need to make developing with Excalibur easier several times on this list. I've been thinking about ways to do this and here are some of my suggestions:
1. A series of short tutorials: We could create a couple short tutorials/introductions somewhat like Picocontainer's "One minute description,Two minute tutorial,Five minute introduction" set. These could be placed in the wiki. 2. Maven plugins like Turbine's META [1]: What about creating a maven plugin that could setup a Fortress or ECM development environment in one command. 3. A simple binary distribution: Unzipping the distribution would give you all the libraries, example configuration files and the Java Service Wrapper already setup. Maybe you could have a couple versions: a lightweight distro which only has a trivial example included versus a "Kitchen Sink" distro that shows how you can tie several components together. 4. Eclipse Plugins: I'm doing some plugin development now and maybe later this year I can write some custom editors for role and configuration files or for generating meta-data or maybe even a graphical editor for wiring up the container (drag and drop the component roles). I'm not sure what type of plugin would be useful, so I'd appreciate some ideas. Also, I think we need to emphasize our relationship with other existing projects more like Turbine, Keel, Cocoon, Xingu, etc. hammett recently said: >I think Spring is twenty years ahead of what we have here - in the sense of >speeding up the development. Well, perhaps. But perhaps not when you consider Turbine and Cocoon and all these other projects which use Excalibur. If we can help users leverage these other libraries and refine Excalibur as an easy to use common platform, then I think we're not in such dire straits. Thoughts? -- jaaron --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
