[japi-compliance-checker] 12/20: New upload

Emmanuel Bourg ebourg-guest at moszumanska.debian.org
Thu May 21 09:04:59 UTC 2015


This is an automated email from the git hooks/post-receive script.

ebourg-guest pushed a commit to branch master
in repository japi-compliance-checker.

commit 490dd6ddae8f569993ababc2a2888098f07c6ce6
Author: Mathieu Malaterre <malat at debian.org>
Date:   Sun Oct 13 13:44:32 2013 +0000

    New upload
---
 debian/changelog                 |   8 ++
 debian/japi-compliance-checker.1 | 254 ---------------------------------------
 debian/rules                     |   6 +-
 3 files changed, 13 insertions(+), 255 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index c9ecefb..4d70e48 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+japi-compliance-checker (1.3.4-1) unstable; urgency=low
+
+  * New upstream
+    + new option -limit-affected
+  * Automate man page generation
+
+ -- Mathieu Malaterre <malat at debian.org>  Sun, 13 Oct 2013 15:41:57 +0200
+
 japi-compliance-checker (1.3.1-1) unstable; urgency=low
 
   * New release
diff --git a/debian/japi-compliance-checker.1 b/debian/japi-compliance-checker.1
deleted file mode 100644
index c8cae91..0000000
--- a/debian/japi-compliance-checker.1
+++ /dev/null
@@ -1,254 +0,0 @@
-.\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.40.9.
-.TH JAPI-COMPLIANCE-CHECKER "1" "May 2012" "japi-compliance-checker API Compliance Checker (Java ACC) 1.1.1" "User Commands"
-.SH NAME
-japi-compliance-checker \- Check backward compatibility of a Java library API
-.SH DESCRIPTION
-.SS "NAME:"
-.IP
-Java API Compliance Checker (japi\-compliance\-checker)
-Check backward compatibility of a Java library API
-.SS "DESCRIPTION:"
-.IP
-Java API Compliance Checker (Java ACC) is a tool for checking backward
-binary/source compatibility of a Java library API. The tool checks classes
-declarations of old and new versions and analyzes changes that may break
-compatibility: removed class members, added abstract methods, etc. Breakage
-of the binary compatibility may result in crashing or incorrect behavior of
-existing clients built with an old version of a library if they run with a
-new one. Breakage of the source compatibility may result in recompilation
-errors with a new library version.
-.IP
-Java ACC 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 a new version of a library).
-.IP
-This tool is free software: you can redistribute it and/or modify it
-under the terms of the GNU LGPL or GNU GPL.
-.SS "USAGE:"
-.IP
-japi\-compliance\-checker [options]
-.SS "EXAMPLE:"
-.IP
-japi\-compliance\-checker \fB\-old\fR OLD.jar \fB\-new\fR NEW.jar
-.IP
-OR
-.IP
-japi\-compliance\-checker \fB\-lib\fR NAME \fB\-old\fR OLD.xml \fB\-new\fR NEW.xml
-OLD.xml and NEW.xml are XML\-descriptors:
-.IP
-<version>
-.IP
-1.0
-.IP
-</version>
-.IP
-<archives>
-.IP
-/path1/to/JAR(s)/
-/path2/to/JAR(s)/
-\&...
-.IP
-</archives>
-.SS "INFORMATION OPTIONS:"
-.HP
-\fB\-h\fR|\-help
-.IP
-Print this help.
-.HP
-\fB\-v\fR|\-version
-.IP
-Print version information.
-.HP
-\fB\-dumpversion\fR
-.IP
-Print the tool version (1.1.1) and don't do anything else.
-.SS "GENERAL OPTIONS:"
-.HP
-\fB\-l\fR|\-lib|\-library <name>
-.IP
-Library name (without version).
-It affects only on the path and the title of the report.
-.HP
-\fB\-d1\fR|\-old|\-o <path(s)>
-.IP
-Descriptor of 1st (old) library version.
-It may be one of the following:
-.IP
-1. Java ARchive (*.jar)
-2. XML\-descriptor (VERSION.xml file):
-.IP
-<version>
-.IP
-1.0
-.IP
-</version>
-.IP
-<archives>
-.IP
-/path1/to/JAR(s)/
-/path2/to/JAR(s)/
-.IP
-\&...
-.IP
-</archives>
-.IP
-\&... (XML\-descriptor template
-.IP
-may be generated by \fB\-d\fR option)
-.IP
-3. API dump generated by \fB\-dump\fR option
-4. Directory with Java ARchives
-5. Comma separated list of Java ARchives
-6. Comma separated list of directories with Java ARchives
-.IP
-If you are using 1, 4\-6 descriptor types then you should
-specify version numbers with \fB\-v1\fR <num> and \fB\-v2\fR <num> options too.
-.IP
-If you are using *.jar as a descriptor then the tool will try to
-get implementation version from MANIFEST.MF file.
-.HP
-\fB\-d2\fR|\-new|\-n <path(s)>
-.IP
-Descriptor of 2nd (new) library version.
-.SS "EXTRA OPTIONS:"
-.HP
-\fB\-client\fR|\-app <path>
-.IP
-This option allows to specify the client Java ARchive that should be
-checked for portability to the new library version.
-.HP
-\fB\-binary\fR
-.IP
-Show "Binary" compatibility problems only.
-Generate report to "bin_compat_report.html".
-.HP
-\fB\-source\fR
-.IP
-Show "Source" compatibility problems only.
-Generate report to "src_compat_report.html".
-.HP
-\fB\-check\-implementation\fR
-.IP
-Compare implementation code (method's body) of Java classes.
-Add 'Problems with Implementation' section to the report.
-.HP
-\fB\-v1\fR|\-version1 <num>
-.IP
-Specify 1st API version outside the descriptor. This option is needed
-if you have prefered an alternative descriptor type (see \fB\-d1\fR option).
-.IP
-In general case you should specify it in the XML descriptor:
-.IP
-<version>
-.IP
-VERSION
-.IP
-</version>
-.HP
-\fB\-v2\fR|\-version2 <num>
-.IP
-Specify 2nd library version outside the descriptor.
-.HP
-\fB\-s\fR|\-strict
-.IP
-Treat all API compatibility warnings as problems.
-.HP
-\fB\-dump\fR|\-dump\-api <descriptor>
-.IP
-Dump library API to gzipped TXT format file. You can transfer it
-anywhere and pass instead of the descriptor. Also it may be used
-for debugging the tool. Compatible dump versions: 1.0<=V<=1.0
-.HP
-\fB\-classes\-list\fR <path>
-.IP
-This option allows to specify a file with a list of classes that should
-be checked, other classes will not be checked.
-.HP
-\fB\-short\fR <path>
-.IP
-Generate short report without 'Added Methods' section.
-.HP
-\fB\-d\fR|\-template
-.IP
-Create XML descriptor template ./VERSION.xml
-.HP
-\fB\-report\-path\fR <path>
-.IP
-Path to compatibility report.
-Default:
-.IP
-compat_reports/<library name>/<v1>_to_<v2>/compat_report.html
-.HP
-\fB\-bin\-report\-path\fR <path>
-.IP
-Path to "Binary" compatibility report.
-Default:
-.IP
-compat_reports/<library name>/<v1>_to_<v2>/bin_compat_report.html
-.HP
-\fB\-src\-report\-path\fR <path>
-.IP
-Path to "Source" compatibility report.
-Default:
-.IP
-compat_reports/<library name>/<v1>_to_<v2>/src_compat_report.html
-.HP
-\fB\-quick\fR
-.IP
-Quick analysis.
-Disabled:
-.IP
-\- analysis of method parameter names
-\- analysis of class field values
-\- analysis of usage of added abstract methods
-.HP
-\fB\-sort\fR
-.IP
-Enable sorting of data in API dumps.
-.SS "OTHER OPTIONS:"
-.HP
-\fB\-test\fR
-.IP
-Run internal tests. Create two incompatible versions of a sample library
-and run the tool to check them for compatibility. This option allows to
-check if the tool works correctly in the current environment.
-.HP
-\fB\-debug\fR
-.IP
-Debugging mode. Print debug info on the screen. Save intermediate
-analysis stages in the debug directory:
-.IP
-debug/<library>/<version>/
-.IP
-Also consider using \fB\-\-dump\fR option for debugging the tool.
-.HP
-\fB\-l\-full\fR|\-lib\-full <name>
-.IP
-Change library name in the report title to <name>. By default
-will be displayed a name specified by \fB\-l\fR option.
-.HP
-\fB\-b\fR|\-browse <program>
-.IP
-Open report(s) in the browser (firefox, opera, etc.).
-.SS "REPORT:"
-.IP
-Compatibility report will be generated to:
-.IP
-compat_reports/<library name>/<v1>_to_<v2>/compat_report.html
-.SS "EXIT CODES:"
-.IP
-0 \- Compatible. The tool has run without any errors.
-non\-zero \- Incompatible or the tool has run with errors.
-.SS "REPORT BUGS TO:"
-.IP
-Andrey Ponomarenko <aponomarenko at rosalab.ru>
-.SS "MORE INFORMATION:"
-.IP
-http://ispras.linuxbase.org/index.php/Java_API_Compliance_Checker
-https://github.com/lvc/japi\-compliance\-checker
-.SH AUTHOR
-Written by Andrey Ponomarenko.
-.SH COPYRIGHT
-Copyright \(co 2012 ROSA Laboratory
-License: LGPL or GPL <http://www.gnu.org/licenses/>
-This program is free software: you can redistribute it and/or modify it.
diff --git a/debian/rules b/debian/rules
index 9f93a7f..7c6a051 100755
--- a/debian/rules
+++ b/debian/rules
@@ -13,7 +13,11 @@ override_dh_install:
 	dh_installdocs doc
 
 debian/japi-compliance-checker.1:
-	help2man --output=$@ --no-info --include=debian/japi-compliance-checker.1.in japi-compliance-checker
+	# remove '.pl' from the generated man page by help2man:
+	ln japi-compliance-checker.pl japi-compliance-checker
+	help2man --output=$@ --no-info --include=debian/japi-compliance-checker.1.in ./japi-compliance-checker
+
+build: debian/japi-compliance-checker.1
 
 get-orig-source:
 	uscan --download --force-download --rename

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-java/japi-compliance-checker.git



More information about the pkg-java-commits mailing list