Free java reporting library software for linux

Java DIME Library project implements Direct Internet Message Encapsulation (DIME), which is a lightweight binary encapsulation format that can be used to encapsulate multiple payloads of arbitrary types and sizes into a single message.
DIME is ideal for incorporating binary attachments into any XML-based protocol. The library fully supports the latest DIME specifications.
Enhancements:
- Corrected DimeRecord.isFirst() thanks to John Russell

Standard Portable Library is a pointer friendly C/C++ STL substitute. The API is similar to Java or .NET and includes common data structures, networking, and database support.

Java Stencil Report is designed to write school reports in a fast way by a set of user-inserted sentences. The project has a small vector graphics editor to create a full customizable print model. Java Stencil Report is designed for schools, but can be used to write any kind of judgement. It does not require any installation.
Enhancements:
- Lines in the print model editor (VectorGraphicsLine) can now be mouse-selected with a more accurate mask.
- VectorGraphicsElement z-depth is now displayed in the status bar.
- A new user friendly dialog for changing the form period was added.
- The placement of VectorGraphicsElement was randomized.
- Transparency was added to the selection border.
- The generic name "Indicator" is now substituted with a more appropriate "Evaluation Wizard" and "Stencil" in all label and the jstecilreport folder.
- A new set of icons was provided in the print model editor.
- Some code was optimized.

Redline RPM Library is a pure Java library for manipulating RPM Package Manager packages. Currently the project supports reading and creating packages and has an included Ant task useful for integration with build systems. Support for package signatures will be added in a future release.
Enhancements:
- A patch has been merged that adds a Maven pom file, the directive for documentation files and directories, and user and group name attributes for files.

Extended Universal Resource Library is a pure Java library for cleaner, more flexible file access in Java.
How data is stored is completely transparent to the client, since the library is meant to replace java.io.File.
It provides implementations for handling local files, Jar/Zip archives, and XML documents. (Implementations for CVS and FTP are available seperately.) Other storage providers can be written and plugged in.
It also provides a merged filesystem implementation that allows multiple hierarchies to appear as one and to override each other in a controlled way. Other features include notification of changes to files, and support for attaching (dynamically updatable) actions to file objects.
Filesystems are an abstraction on top of java.io.File (in the case of local files), that provide a number of useful things:
- File storage is completely abstracted - third parties can create support for access to file-like objects stored in an arbitrary manner, such as in a database, or in a version control system.
- Built-in support for ZIP/JAR archives and XML-based filesystems and the ability to transparently use other filesystems supported by NetBeans (such as the FTP filesystem) by adding the necessary classes
- Supports listening for change events if a file is externally modified
- Ability to add arbitrary "status" data to a file object and be notified of changes on it
- Support for actions on file objects, allowing you to define what actions are possible on a given file (and dynamically update these), and then expose those actions through your user interface.

DM1 Thread Library is part of the DM1 project. This library was born out of my need to have a portable C++ Thread library that would be simple to use, and would provide all the necessary Threads functionality I required for the DM1 project.
Initially, this library was in C, but when I decided to re-write DM1 in C++, I ported the library to C++. During the port, I enhanced the functionality of the Threads library.
The DM1 Threads library aims to be small. It does not try to provide a comprehensive set of functionality, but only what is absolutely essential for a project like DM1. I had the simplicity of the Java Threads package in mind when creating this library.
The constructs provided by the DM1 Thread library are:
- Thread objects that represent Operating System threads.
- A Mutex is provided as a mechanism for Mutual Exclusion . Mutexes are used to ensure that a piece of code is executed by only one thread at any point in time.
- Events are provided as low-level mechanisms for thread synchronisation. Events can be waited for, and signalled to.
- A higher level object, that combines the functionality of an Event and a Mutex, is provided. This is the Monitor object. A Monitor can be locked exclusively, just like a Mutex, but it can also be made the object of a Wait operation. The signalling mechanism supports notification of one or more waiting threads.
- To enable more efficient locking when both shared and exclusive access to data is required, Latches are provided.
- Apart from the Thread synchronisation primitives described above, the library also provides a ThreadPool for the situation when it is inefficient to create a thread exclusively for a particular task, and it is desirable to share a pool of threads for executing multiple tasks.
Design Principles
The DM1 Threads library was designed with the following principles in mind:
1. Implement the bare minimum that is required. This Threads library does not aim to be a comprehensive threads package.
2. Avoid complex algorithms. If a particular construct is hard to implement correctly on all platforms, avoid it.
3. Document the library.
4. Avoid low level code, such as assembler code to implement Spin locks. Rely on the libraries provided by the Operating System.
5. Avoid holding Mutexes beyond function calls. A DM1 Thread library function will not hold any Mutex locks when it returns.
6. Avoid using clever C++ techniques wherever possible. (Unfortunately, some cleverness is required to implement the Thread class correctly).
7. Avoid dependency on external libraries. The DM1 library only requires the standard C library, apart from native Threads functionality.
8. Always report an error as soon as it is discovered.
9. Insert debug messages that can be switched on at run-time.
10. Do not throw exceptions from destructors because these might be executing as a result of an uncaught exception.
11. Never let an error go unreported.

Java Network Stack provides a Java library for research oriented network programming.

Java Network Stack is a library used by the DIMES project to create new internet measurements. It provides a clean API for packet manipulation, send, receive, filter, and analysis. It is a unification of raw socket capabilities, MAC level networkingm, and IPv6 capabilities.

JasperReports is a powerful open source Java reporting tool that has the ability to deliver rich content onto the screen, to the printer or into PDF, HTML, XLS, CSV and XML files.
It is entirely written in Java and can be used in a variety of Java enabled applications, including J2EE or Web applications, to generate dynamic content.
JasperReports is main purpose is to help creating page oriented, ready to print documents in a simple and flexible manner.
Main features:
- Report Design
- Header Sections
- Footer Sections
- Columns
- Groups
- Calculations
- Text format
- Images
Enhancements:
- This version introduces support for external style templates, a new report section for better control over empty reports, an enhanced XLS exporter, and various bugfixes and improvements.