Peter Donald wrote:
Berin Loritsch wrote:
Ok, just need a little clarification here. Are you saying we do the work of integration first to see what would break before doing a relese?
yep.
I am using Fortress for my GUIApp framework project. This provides a decent test bed, but it doesn't excersize all of Fortress' features.
kool. But to be honest I would prefer it to be someone who has no contact with event so they don't make any assumptions about new event structure so if there is any incompatibilities they will pick them up.
Ok.
Since I just got everything ready for Maven to build the project, I can do the work of integration and allow whoever wills to stress test it.
There might be one minor sticky point: most clients that interact with the CommandManager would do so through the use of the org.apache.excalibur.event.Sink interface which would cause some binary compatibility issues. I could copy that interface into the Fortress directory in the same package to maintain that binary compatibility.
It's ugly, and it should be deprecated, but it is a fact of how most of the integration was done. The good news is that there are only a few things that use the CommandManager/Sink directly and almost all of them are directly in Fortress itself.
Any insights on how to do this as non-intrusively as possible?
--
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."
- Rich Cook
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
