1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
Source: libspi-java
Section: java
Priority: optional
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders: Jakub Adam <jakub.adam@ktknet.cz>,
tony mancill <tmancill@debian.org>
Build-Depends: debhelper (>= 11), default-jdk, javahelper
Standards-Version: 4.4.0
Vcs-Git: https://salsa.debian.org/java-team/libspi-java.git
Vcs-Browser: https://salsa.debian.org/java-team/libspi-java
Homepage: https://github.com/rspilker/spi
Package: libspi-java
Architecture: all
Depends: ${java:Depends}, ${misc:Depends}
Description: 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.
Package: libspi-java-doc
Section: doc
Architecture: all
Depends: ${java:Depends}, ${misc:Depends}
Description: 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.
|
