libspi-java 0.2.4-2 source package in Ubuntu

Changelog

libspi-java (0.2.4-2) unstable; urgency=medium

  * Team upload.
  * Add myself to Uploaders
  * Use debhelper and compat level 10
  * Bump Standards-Version to 3.9.8
  * Add support for SOURCE_DATE_EPOCH for reproducible builds.
    Build-deps of libspi-java will now use SOURCE_DATE_EPOCH instead of
    embedding the current build timestamp in META-INF/services/* files.
    (Closes: #872065)

 -- tony mancill <email address hidden>  Sun, 13 Aug 2017 20:58:20 -0700

Upload details

Uploaded by:
Debian Java Maintainers
Uploaded to:
Sid
Original maintainer:
Debian Java Maintainers
Architectures:
all
Section:
misc
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Bionic release universe misc

Builds

Artful: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
libspi-java_0.2.4-2.dsc 2.0 KiB 197c4236a371ede52c0727c64a6d036b19807452bb6a4f25735bd2460513e11b
libspi-java_0.2.4.orig.tar.gz 7.4 KiB a242f6d368743a207878e492b86cc0d5e4083f1e053922e29c4ae69babcb30a6
libspi-java_0.2.4-2.debian.tar.xz 2.5 KiB 74d28b8659f82c2e05111a302266396009db87b1b81f39cbf9aa934ce2f16b42

Available diffs

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.