libspi-java 0.2.4-1 source package in Ubuntu
Changelog
libspi-java (0.2.4-1) unstable; urgency=low * Initial release. (Closes: #807874) -- Jakub Adam <email address hidden> Fri, 02 Nov 2012 21:28:02 +0100
Upload details
- Uploaded by:
- Debian Java Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Java Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Low Urgency
See full publishing history Publishing
| Series | Published | Component | Section | |
|---|---|---|---|---|
| Xenial | release | universe | misc |
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| libspi-java_0.2.4-1.dsc | 2.0 KiB | 88afaa44f543ec025548c8035c037147fb927af9fd82f1a5b7fc25956dffc840 |
| libspi-java_0.2.4.orig.tar.gz | 7.4 KiB | a242f6d368743a207878e492b86cc0d5e4083f1e053922e29c4ae69babcb30a6 |
| libspi-java_0.2.4-1.debian.tar.xz | 1.8 KiB | ba387165605e85899e898b3a7a89f13f8d6f9fa54b5a9209bcd80c28ca61b2af |
No changes file available.
Binary packages built by this source
- libspi-java: Simplifies usage of Java Service Provider Interface
The usage of the Service Provider Interface in Java is a great way to make your
program more extensible. However, implementing and distributing such an
Interface is error prone.
.
One of the reasons is that the system depends on naming schemes and text files.
The name of an implementation should be put in a text file, located on the
classpath in a folder called META-INF/services/ <qualified interface name>.
.
This project allows the programmer to use an Annotation, @ProviderFor, to flag
a class as an implementation of a certain interface. During compilation, the
necessary files are created at the appropriate locations. Also, the class is
inspected to see if it follows all rules applicable to Service Providers.
Compile time errors will be generated if those rules are broken, assisting the
programmer to create more robust code.
- libspi-java-doc: Documentation for libspi-java
The usage of the Service Provider Interface in Java is a great way to make your
program more extensible. However, implementing and distributing such an
Interface is error prone.
.
One of the reasons is that the system depends on naming schemes and text files.
The name of an implementation should be put in a text file, located on the
classpath in a folder called META-INF/services/ <qualified interface name>.
.
This project allows the programmer to use an Annotation, @ProviderFor, to flag
a class as an implementation of a certain interface. During compilation, the
necessary files are created at the appropriate locations. Also, the class is
inspected to see if it follows all rules applicable to Service Providers.
Compile time errors will be generated if those rules are broken, assisting the
programmer to create more robust code.
.
This package contains the generated API documentation.
