File: control

package info (click to toggle)
japi-compliance-checker 2.4-2
  • links: PTS, VCS
  • area: main
  • in suites: bullseye, buster
  • size: 648 kB
  • sloc: perl: 8,569; xml: 2,825; makefile: 29
file content (29 lines) | stat: -rw-r--r-- 1,487 bytes parent folder | download
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
Source: japi-compliance-checker
Section: devel
Priority: optional
Build-Depends: debhelper (>= 11), help2man
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders: Emmanuel Bourg <ebourg@apache.org>,
 tony mancill <tmancill@debian.org>
Standards-Version: 4.2.1
Vcs-Git: https://salsa.debian.org/java-team/japi-compliance-checker.git
Vcs-Browser: https://salsa.debian.org/java-team/japi-compliance-checker
Homepage: https://lvc.github.io/japi-compliance-checker/

Package: japi-compliance-checker
Architecture: all
Multi-Arch: foreign
Depends: ${perl:Depends}, ${misc:Depends}
Recommends: default-jdk
Description: tool to compare compatibility of Java library API
 Java API Compliance Checker (Java ACC) is a tool for checking backward binary
 and source-level compatibility of a Java library API. The tool checks classes
 declarations of old and new versions and analyzes changes that may break
 compatibility: removed methods, removed class fields, added abstract methods,
 etc. Binary incompatibility may result in crashing or incorrect behavior of
 existing clients built with an old version of a library when they are running
 with a new one. Source incompatibility may result in recompilation errors with
 a new library version. The tool is intended for library developers and
 operating system maintainers who are interested in ensuring backward
 compatibility, i.e. allow old clients to run or to be recompiled with newer
 library versions.