| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| Library | 2024-06-22 | ||
| Source Code | 2024-06-22 | ||
| Tools | 2024-06-22 | ||
| Documentation | 2024-06-22 | ||
| README.txt | 2024-06-22 | 2.2 kB | |
| Totals: 5 Items | 2.2 kB | 0 | |
eBus 7.3.0 Downloads
________________________________________________________________________________
*** ATTENTION ***
As of release 6.0.0, eBus is now based on Java 11.
eBus does *not* use modules at this time. Therefore include
eBus jars in -classpath and not -modulepath.
The eBus license also converted from LGPL 2.1 to
Apache License 2.0. The reason for the license change is
due to Apache License 2.0 being more end-user friendly that
LGPL 2.1.
________________________________________________________________________________
Release 7.3.0 made the following changes:
Feature Requests:
+ Ticket 33: Switch to org.slf4j logging framework.
Since its inception, eBus used java.util.logging framework
since that was the only framework guaranteed to be available
20 years ago.
With the rise of Maven and Gradle, other logging frameworks
are easily obtained. Given this, eBus API now uses slf4j,
a logging framework which supports any number of underlying
logging frameworks. This means that eBus will use the logging
framework the application chooses.
+ Ticket 34: net.sf.eBus.timer package.
net.sf.eBus.timer.EScheduledTimer works with the eBus
dispatcher framework so that when a scheduled task expires,
that task is placed on the associated eBus objects task queue
and the eBus object is dispatched. That means the eBus object
maintains its effective single threaded nature which eBus
dispatcher guarantees.
Using timers like java.util.Timer or
java.util.concurrent.ScheduledExecutorService introduces
threads outside eBus dispatcher and so an eBus object becomes
multi-threaded, requiring thread coordination.
Bugs:
(No bug fixes.)
There are four download folders:
+ Library: contains the eBus API jar files.
+ Documentation: contains the eBus Programmer's Manul in PDF and
Javadoc folders in tar, gzipped and zip formats.
+ Source Code: snapshot of eBus maven project files at release
time.
+ Tools: contains the eBus GUI application and configuration file
needed to run the application.