|Download||download from SourceForge|
Pronto is a Java library that has is being developed with the following aims:
In this context, a Java application could be anything from a Swing based program to a headless dæmon; modestly sized might mean applications with classes which number in the dozens or hundreds. What Pronto is not for is small Java "utilities" (which will see no benefits) nor enterprise level applications (which need something more powerful).
In short, pronto aims to provide Java application developers with a shortcut from a piece of code which does something useful, to an application that can be reliably started/stopped, configured and logged. It is expected that the applications to most benefit are those which must provide extended unbroken periods of reliable execution during which their environment and operational parameters may need to vary.
Pronto is released under the GNU Lesser General Public License (version 2). Under this licence, your freedoms to use this software are protected without preventing its use in non-free applications to the extent permitted by the license.
Pronto is envisioned to be largely composed of five modules with the intention being that developers will be able use their functionality independently of Pronto's usefulness as an application 'host'. The five main areas of functionality are anticipated to be:
Only the implementation of the logging and run-level modules remains.
Pronto's development is managed using Maven 2. Consequently, a maven generated site is available that provides reference information. It includes project dependencies, javadocs and cross-referenced source code.
The compiled Pronto code is currently packaged as a small collection of jars named module-x.x.jar. For each such jar there is a corresponding source code jar (module-x.x-sources.jar) and documentation jar (module-x.x-javadoc.jar). This arrangement allows the modules to be used independently where necessary.
When the project is code-complete, Pronto will be able to act as a host for Java application code, at that time, the packaging will be reviewed with the aim of ensuring that application deployment is straightforward. This anticipated change will not prevent the direct use of Pronto modules; Pronto will always be usable in both modes.
At present, Pronto does not have any external dependencies. It requires Java 1.5.
There are no established time frames for Pronto's development but there is a clear development plan:
At the current rate of development, Pronto should be code complete around the start of Q2 2007. However, a consequence of 3 above is that there will probably be a significant delay between the first robust implementations (version 0.6+) and the first proper release (version 1.0).
|0.1||2006-09-26||Contains initial version of configuration module.|
|0.2||2006-10-30||Contains first version of state transition API.|
|0.3||2006-12-31||Features initial version of control module.|
|0.4||2007-01-xxx||Introduces a logging configuration library.|
|0.5||-||Run-level library for managing tiered class loading.|
|0.6||-||Fully determined file structures and configuration.|
|0.7||-||First attempt to finalize API interfaces.|
|0.8||-||Adjustments based on feedback from use.|