It has been brought to my attention that the Event package was processing events and commands through the pipeline in LIFO order. Thanks to Niklas Therning, this issue was caught and everything is processed in FIFO order now. A new testcase and the fix has been made.
On one hand I want to oppologize for the frequency of updates for this project, but on the other hand, I don't want to hold up fixes that others are depending on. The good news is that the changes are not large and the issues are relatively minor.
Note that this particular issue is not one that seriously impacts Excalibur all that much due to the nature of the way Fortress uses the package. It affects people who use a SEDA like approach and depend on things arriving close to the proper order (allowing for multithreaded shuffling).
It is available, and up on the D-Haven servers.
You will have to change your Maven dependency on Event like this:
<dependency> <groupId>d-haven-event</groupId>
<!-- New artifact id! --> <artifactId>d-haven-event</artifactId>
<version>1.0.3</version> </dependency>
This is to get closer to the standards in place already and play nicer in the Maven environment.
--
"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/
