One thing the changeover to Avalon/Fortress proved is that we need a new Event released, or at least a snapshot released. The new failure handler is what is causing the maven build to crash, which makes development difficult.
Ok, I have found out that in the short period of time since Fortress was released that a few things were altered in dependent libraries which caused compilation issues in Fortress:
1) Excalibur-Logger and its Log4J integration. Some of the integration changes were specific to the new Excalibur-Logger.
2) Avalon Framework. Framework's DefaultConfigurationBuilder has a new method so that we can provide a "SystemID" value so that error messages are a little more friendly.
3) Excalibur Event and the CommandFailureHandler.
This is all well and good, but with Maven it adds some complications. In order for things to continue to build, we need to upload a snapshot jar, and modify the project.xml to depend on that snapshot.
There are three things that come out of this:
1) We know which dependent libraries need to be updated (i.e. the ones with a snapshot version [yyyymmdd])
2) The new version of Fortress is dependent on these new versions of the libraries.
3) Maven encourages you to only work with released JARs instead of the latest and greatest--although you can work around it easily enough).
If we are all OK with this, I would like to remind all that we need to be careful with how many JARs we force our users to upgrade at one time.
Lastly, what about creating the "BIG JAR" where all of Fortress's dependencies were included?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
