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 d251b38e4bc1dd1fd48ec4a1b818ea675dc279ff Author: Mathieu Malaterre <[email protected]> Date: Thu Apr 26 12:56:05 2012 +0000 Cleanups JACC --- debian/abi-compliance-checker.1 | 155 ------------------------ debian/changelog | 4 +- debian/japi-compliance-checker.1 | 250 +++++++++++++++++++++++++++++++++++++++ debian/manpages | 2 +- debian/rules | 6 +- 5 files changed, 256 insertions(+), 161 deletions(-) diff --git a/debian/abi-compliance-checker.1 b/debian/abi-compliance-checker.1 deleted file mode 100644 index 70a4829..0000000 --- a/debian/abi-compliance-checker.1 +++ /dev/null @@ -1,155 +0,0 @@ -.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.40.6. -.TH ABI "1" "March 2012" "ABI Compliance Checker (ACC) 1.96.8" "User Commands" -.SH NAME -ABI \- manual page for ABI Compliance Checker (ACC) 1.96.8 -.SH DESCRIPTION -.SS "NAME:" -.IP -ABI Compliance Checker (abi\-compliance\-checker) -Check backward binary compatibility of a shared C/C++ library API -.SS "DESCRIPTION:" -.IP -ABI Compliance Checker (ACC) is a tool for checking backward binary -compatibility of a shared C/C++ library API. The tool checks header -files and shared libraries (*.so) of old and new versions and -analyzes changes in Application Binary Interface (ABI=API+compiler ABI) -that may break binary compatibility: changes in calling stack, v\-table -changes, removed symbols, etc. Binary incompatibility may result in -crashing or incorrect behavior of applications built with an old version -of a library if they run on a new one. -.IP -The tool is intended for library developers and OS maintainers who are -interested in ensuring binary compatibility, i.e. allow old applications -to run with new library versions without the need to recompile. Also it -can be used by ISVs for checking applications portability to new library -versions. Found issues can be taken into account when adapting the -application to a new library version. -.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 -abi\-compliance\-checker [options] -.SS "EXAMPLE:" -.IP -abi\-compliance\-checker \fB\-lib\fR NAME \fB\-d1\fR OLD.xml \fB\-d2\fR NEW.xml -.IP -OLD.xml and NEW.xml are XML\-descriptors: -.IP -<version> -.IP -1.0 -.IP -</version> -.IP -<headers> -.IP -/path1/to/header(s)/ -/path2/to/header(s)/ -.IP -\&... -.IP -</headers> -.IP -<libs> -.IP -/path1/to/library(ies)/ -/path2/to/library(ies)/ -.IP -\&... -.IP -</libs> -.SS "INFORMATION OPTIONS:" -.HP -\fB\-h\fR|\-help -.IP -Print this help. -.HP -\fB\-i\fR|\-info -.IP -Print complete info. -.HP -\fB\-v\fR|\-version -.IP -Print version information. -.HP -\fB\-dumpversion\fR -.IP -Print the tool version (1.96.8) 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> -.IP -Descriptor of 1st (old) library version. -It may be one of the following: -.IP -1. XML\-descriptor (VERSION.xml file): -.IP -<version> -.IP -1.0 -.IP -</version> -.IP -<headers> -.IP -/path1/to/header(s)/ -/path2/to/header(s)/ -.IP -\&... -.IP -</headers> -.IP -<libs> -.IP -/path1/to/library(ies)/ -/path2/to/library(ies)/ -.IP -\&... -.IP -</libs> -.IP -\&... (XML\-descriptor template -.IP -can be generated by \fB\-d\fR option) -.IP -2. ABI dump generated by \fB\-dump\fR option -3. Directory with headers and/or shared libraries -4. Single header file -5. Single shared library -6. Comma separated list of headers and/or libraries -.IP -If you are using an 2\-6 descriptor types then you should -specify version numbers with \fB\-v1\fR <num> and \fB\-v2\fR <num> options too. -.IP -For more information, please see: -.IP -http://ispras.linux\-foundation.org/index.php/Library_Descriptor -.HP -\fB\-d2\fR|\-new|\-n <path> -.IP -Descriptor of 2nd (new) library version. -.HP -\fB\-dump\fR|\-dump\-abi <descriptor path(s)> -.IP -Dump library ABI to gzipped TXT format file. You can transfer it -anywhere and pass instead of the descriptor. Also it can be used -for debugging the tool. Compatible dump versions: 2.0<=V<=2.10.1 -.HP -\fB\-old\-dumps\fR -.IP -Enable support for old\-version ABI dumps (1.18<=V<2.0). -.SS "MORE INFO:" -.IP -abi\-compliance\-checker \fB\-\-info\fR -.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/changelog b/debian/changelog index 9fd3c61..3bcbf6d 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,5 +1,5 @@ japi-compliance-checker (1.1-1) unstable; urgency=low - * Initial release (Closes: #540247) + * Initial release (Closes: #) - -- Mathieu Malaterre <[email protected]> Thu, 26 Apr 2012 14:42:42 +0200 + -- Mathieu Malaterre <[email protected]> Thu, 26 Apr 2012 14:50:35 +0200 diff --git a/debian/japi-compliance-checker.1 b/debian/japi-compliance-checker.1 new file mode 100644 index 0000000..510508f --- /dev/null +++ b/debian/japi-compliance-checker.1 @@ -0,0 +1,250 @@ +.\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.38.2. +.TH JAVA "1" "April 2012" "Java API Compliance Checker (Java ACC) 1.1" "User Commands" +.SH NAME +JAVA \- manual page for Java API Compliance Checker (Java ACC) 1.1 +.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) 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 +.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 <[email protected]> +.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/manpages b/debian/manpages index 500daf2..77fa025 100644 --- a/debian/manpages +++ b/debian/manpages @@ -1 +1 @@ -debian/abi-compliance-checker.1 +debian/japi-compliance-checker.1 diff --git a/debian/rules b/debian/rules index cac9d03..a2fa393 100755 --- a/debian/rules +++ b/debian/rules @@ -10,12 +10,12 @@ override_dh_auto_install: override_dh_install: dh_install usr/bin - dh_install usr/share/abi-compliance-checker/ + #dh_install usr/share/abi-compliance-checker/ # docs: dh_installdocs doc -debian/abi-compliance-checker.1: - help2man --output=$@ --no-info abi-compliance-checker +debian/japi-compliance-checker.1: + help2man --output=$@ --no-info japi-compliance-checker 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 _______________________________________________ pkg-java-commits mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-commits
