A couple of days ago I commited some updated to the excalibur-event package. The update was a replacement of the maven build descriptor and the seperation of the package into an "api" and "impl". I would be interested in getting feedback from people who know this package concerning the seperation I have done. There are perhaps interfaces that I have included in the api group that don't get exposed and could be moved into the impl package.
During the process I stripped down the dependencies to just the stuff needed to build (which was massively smaller than the ant build depedencies). I then added the test cases - but this created some problems. What I discovered is that the dependency between event and pool is on four mpool test cases. In the update that I committed, I did not include the mpool test cases because I wanted to get clarification on what the relationship between excalibur-event and excalibur-pool really is.
Any pearls of wisdom appreciated.
The only real connection between the two is that the Event package recognizes the Releasable/Recyclable interface where we clean up a component on entry back into the pool. There is equivalent functionality native to MPool, but it is a compatibility mechanism via reflection. That is why the package is not needed during compilation.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
