debian/0000755000000000000000000000000012103534274007167 5ustar debian/jsdoc-toolkit.manpages0000644000000000000000000000001711523765545013503 0ustar debian/jsdoc.1 debian/jsdoc.10000644000000000000000000001204512103533072010350 0ustar '\" t .\" Title: JSDOC-TOOLKIT .\" Author: Georges Khaznadar .\" Generator: DocBook XSL Stylesheets v1.76.1 .\" Date: 02/03/2013 .\" Manual: jsdoc-toolkit User Manual .\" Source: jsdoc-toolkit .\" Language: English .\" .TH "JSDOC\-TOOLKIT" "1" "02/03/2013" "jsdoc-toolkit" "jsdoc-toolkit User Manual" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .\" http://bugs.debian.org/507673 .\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html .\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" ----------------------------------------------------------------- .\" * set default formatting .\" ----------------------------------------------------------------- .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) .ad l .\" ----------------------------------------------------------------- .\" * MAIN CONTENT STARTS HERE * .\" ----------------------------------------------------------------- .SH "NAME" jsdoc \- automatic generator for HTML documentation of Javascript sources .SH "SYNOPSIS" .HP \w'\fBjsdoc\fR\ 'u \fBjsdoc\fR {\fB\-d=\fR\fB\fI\fR\fR\ |\ \fB\-\-directory=\fR\fB\fI\fR\fR} [\fBoptions\fR] \fB\fR \fB\&.\&.\&.\fR .HP \w'\fBjsdoc\fR\ 'u \fBjsdoc\fR [{\fB\-h\fR\ |\ \fB\-\-help\fR}] .SH "DESCRIPTION" .PP This manual page documents briefly the \fBjsdoc\fR command\&. .PP \fBjsdoc\fR is application, written in JavaScript, for automatically generating template\-formatted, multi\-page HTML (or XML, JSON, or any other text\-based) documentation from commented JavaScript source code\&. .SH "OPTIONS" .PP The program follows the usual GNU command line syntax, with long options starting with two dashes (`\-\*(Aq)\&. A summary of options is included below\&. For a complete description, see the \fBinfo\fR(1) files\&. .PP \fB\-a\fR, \fB\-\-allfunction\fR .RS 4 Include all functions, even undocumented ones\&. .RE .PP \fB\-c\fR, \fB\-\-conf\fR .RS 4 Load a configuration file\&. .RE .PP \fB\-d=\fR\fB\fI\fR\fR, \fB\-\-directory=\fR\fB\fI\fR\fR .RS 4 Output to this directory (required parameter)\&. .RE .PP \fB\-D=\fR\fB\fI"myVar:My\ \&value"\fR\fR, \fB\-\-define=\fR\fB\fI"myVar:My\ \&value"\fR\fR .RS 4 Multiple\&. Define a variable, available in JsDoc as JSDOC\&.opt\&.D\&.myVar\&. .RE .PP \fB\-e=\fR\fB\fI\fR\fR, \fB\-\-encoding=\fR\fB\fI\fR\fR .RS 4 Use this encoding to read and write files\&. .RE .PP \fB\-E=\fR\fB\fI"REGEX"\fR\fR, \fB\-\-exclude=\fR\fB\fI"REGEX"\fR\fR .RS 4 Multiple\&. Exclude files based on the supplied regex\&. .RE .PP \fB\-h\fR, \fB\-\-help\fR .RS 4 Show this message and exit\&. .RE .PP \fB\-m\fR, \fB\-\-multiples\fR .RS 4 Don\*(Aqt warn about symbols being documented more than once\&. .RE .PP \fB\-n\fR, \fB\-\-nocode\fR .RS 4 Ignore all code, only document comments with @name tags\&. .RE .PP \fB\-o=\fR\fB\fI\fR\fR, \fB\-\-out=\fR\fB\fI\fR\fR .RS 4 Print log messages to a file (defaults to stdout)\&. .RE .PP \fB\-p\fR, \fB\-\-private\fR .RS 4 Include symbols tagged as private, underscored and inner symbols\&. .RE .PP \fB\-q\fR, \fB\-\-quiet\fR .RS 4 Do not output any messages, not even warnings\&. .RE .PP \fB\-r=\fR\fB\fI\fR\fR, \fB\-\-recurse=\fR\fB\fI\fR\fR .RS 4 Descend into src directories\&. .RE .PP \fB\-s\fR, \fB\-\-suppress\fR .RS 4 Suppress source code output\&. .RE .PP \fB\-S\fR, \fB\-\-securemodules\fR .RS 4 Use Secure Modules mode to parse source code\&. .RE .PP \fB\-t=\fR\fB\fI\fR\fR, \fB\-\-template=\fR\fB\fI\fR\fR .RS 4 Use this template to format the output\&. .RE .PP \fB\-T\fR, \fB\-\-test\fR .RS 4 Run all unit tests and exit\&. .RE .PP \fB\-u\fR, \fB\-\-unique\fR .RS 4 Force file names to be unique, but not based on symbol names\&. .RE .PP \fB\-v\fR, \fB\-\-verbose\fR .RS 4 Provide verbose feedback about what is happening\&. .RE .PP \fB\-x=\fR\fB\fI[,EXT]\&.\&.\&.\fR\fR, \fB\-\-ext=\fR\fB\fI[,EXT]\&.\&.\&.\fR\fR .RS 4 Scan source files with the given extension/s (defaults to js)\&. .RE .SH "BUGS" .PP The following bugs are known bugs: .PP Does not support spaces in arguments .RS 4 The wrapper \fBjsdoc\fR is not immune to spaces in filenames, either escaped or not\&. .RE .SH "AUTHOR" .PP \fBGeorges Khaznadar\fR <\&georgesk@ofset\&.org\&> .RS 4 Wrote this manpage for the Debian system\&. .RE .SH "COPYRIGHT" .br Copyright \(co 2011 Georges Khaznadar .br .PP This manual page was written for the Debian system (and may be used by others)\&. .PP Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation\&. .PP On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common\-licenses/GPL\-2\&. .sp debian/jsdoc-toolkit.install0000644000000000000000000000023511523737043013350 0ustar jsdoc-toolkit/java/build/jar/jsrun.jar /usr/share/java jsdoc /usr/bin jsdoc-toolkit/app jsdoc-toolkit/templates jsdoc-toolkit/conf /usr/share/jsdoc-toolkit debian/patches/0000755000000000000000000000000011610323264010613 5ustar debian/patches/series0000644000000000000000000000004511610323107012023 0ustar 10jsdoc.patch 20TokenReader.js.patch debian/patches/20TokenReader.js.patch0000644000000000000000000000473411610323160014617 0ustar Index: jsdoc-toolkit-2.4.0+dfsg/jsdoc-toolkit/app/lib/JSDOC/TokenReader.js =================================================================== --- jsdoc-toolkit-2.4.0+dfsg.orig/jsdoc-toolkit/app/lib/JSDOC/TokenReader.js +++ jsdoc-toolkit-2.4.0+dfsg/jsdoc-toolkit/app/lib/JSDOC/TokenReader.js @@ -13,31 +13,31 @@ JSDOC.TokenReader = function() { @type {JSDOC.Token[]} */ JSDOC.TokenReader.prototype.tokenize = function(/**JSDOC.TextStream*/stream) { - var tokens = []; - /**@ignore*/ tokens.last = function() { return tokens[tokens.length-1]; } - /**@ignore*/ tokens.lastSym = function() { - for (var i = tokens.length-1; i >= 0; i--) { - if (!(tokens[i].is("WHIT") || tokens[i].is("COMM"))) return tokens[i]; - } + var tokens = []; + /**@ignore*/ tokens.last = function() { return tokens[tokens.length-1]; }; + /**@ignore*/ tokens.lastSym = function() { + for (var i = tokens.length-1; i >= 0; i--) { + if (!(tokens[i].is("WHIT") || tokens[i].is("COMM"))) return tokens[i]; } + }; - while (!stream.look().eof) { - if (this.read_mlcomment(stream, tokens)) continue; - if (this.read_slcomment(stream, tokens)) continue; - if (this.read_dbquote(stream, tokens)) continue; - if (this.read_snquote(stream, tokens)) continue; - if (this.read_regx(stream, tokens)) continue; - if (this.read_numb(stream, tokens)) continue; - if (this.read_punc(stream, tokens)) continue; - if (this.read_newline(stream, tokens)) continue; - if (this.read_space(stream, tokens)) continue; - if (this.read_word(stream, tokens)) continue; - - // if execution reaches here then an error has happened - tokens.push(new JSDOC.Token(stream.next(), "TOKN", "UNKNOWN_TOKEN")); - } - return tokens; -} + while (!stream.look().eof) { + if (this.read_mlcomment(stream, tokens)) continue; + if (this.read_slcomment(stream, tokens)) continue; + if (this.read_dbquote(stream, tokens)) continue; + if (this.read_snquote(stream, tokens)) continue; + if (this.read_regx(stream, tokens)) continue; + if (this.read_numb(stream, tokens)) continue; + if (this.read_punc(stream, tokens)) continue; + if (this.read_newline(stream, tokens)) continue; + if (this.read_space(stream, tokens)) continue; + if (this.read_word(stream, tokens)) continue; + + // if execution reaches here then an error has happened + tokens.push(new JSDOC.Token(stream.next(), "TOKN", "UNKNOWN_TOKEN")); + } + return tokens; +}; /** @returns {Boolean} Was the token found? debian/patches/10jsdoc.patch0000644000000000000000000000730011610323023013070 0ustar Index: jsdoc-toolkit-2.4.0+dfsg/jsdoc =================================================================== --- /dev/null +++ jsdoc-toolkit-2.4.0+dfsg/jsdoc @@ -0,0 +1,73 @@ +#!/bin/sh + +# launcher script for jsdoc +# Author: Avi Deitcher +# Modified by Georges Khaznadar +# +# This program is released under the MIT License as follows: + +# Copyright (c) 2008-2009 Atomic Inc +# Copyright (c) 2011 Georges Khaznadar +# +#Permission is hereby granted, free of charge, to any person +#obtaining a copy of this software and associated documentation +#files (the "Software"), to deal in the Software without +#restriction, including without limitation the rights to use, +#copy, modify, merge, publish, distribute, sublicense, and/or sell +#copies of the Software, and to permit persons to whom the +#Software is furnished to do so, subject to the following +#conditions: +## +#The above copyright notice and this permission notice shall be +#included in all copies or substantial portions of the Software. +# +#THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, +#EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES +#OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND +#NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT +#HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +#WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING +#FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR +#OTHER DEALINGS IN THE SOFTWARE. +# + +check_mandatory_option(){ + for a in "$@"; do + if [ "$a" = -h ] || [ "$a" = --help ]; then ok=1; fi + outdir=$(echo "$a" | sed -n 's/-d=\(.\+\)/-d="\1"/p') + if [ -n "$outdir" ]; + then + ok=1 + else + outdir=$(echo "$a" | sed -n 's/--directory=\(.\+\)/--directory="\1"/p') + if [ -n "$outdir" ]; + then + ok=1 + fi + fi + done + + if ! [ "$ok" = 1 ]; then + echo "An argument like -d= or --directory= is mandatory!" + echo "Try 'jsdoc --help' or 'man jsdoc' for more information." + exit 1 + fi +} + +check_mandatory_option $@ + +if [ -n "$JSDOCDIR" ]; then + _DOCDIR="-Djsdoc.dir=$JSDOCDIR" +else + _DOCDIR="" +fi + +if [ -n "$JSDOCTEMPLATEDIR" ]; then + _TDIR="-Djsdoc.template.dir=$JSDOCTEMPLATEDIR" +else + _TDIR="-Djsdoc.template.dir=/usr/share/jsdoc-toolkit/templates/jsdoc" +fi + +CMD="java $_DOCDIR $_TDIR -jar /usr/share/java/jsrun.jar /usr/share/jsdoc-toolkit/app/run.js $@" +echo $CMD +$CMD Index: jsdoc-toolkit-2.4.0+dfsg/jsdoc-toolkit/java/build.xml =================================================================== --- jsdoc-toolkit-2.4.0+dfsg.orig/jsdoc-toolkit/java/build.xml +++ jsdoc-toolkit-2.4.0+dfsg/jsdoc-toolkit/java/build.xml @@ -7,7 +7,7 @@ @@ -16,7 +16,7 @@ - + @@ -26,7 +26,7 @@ - + debian/control0000644000000000000000000000142112103526730010566 0ustar Source: jsdoc-toolkit Section: devel Priority: extra Maintainer: Georges Khaznadar Build-Depends: debhelper (>= 7.0.50~), quilt, ant, default-jdk, rhino, xsltproc, docbook-xsl Standards-Version: 3.9.3 Homepage: http://code.google.com/p/jsdoc-toolkit/ Package: jsdoc-toolkit Architecture: all Depends: ${misc:Depends}, rhino Description: automatic generator for HTML documentation of Javascript sources JsDoc Toolkit is an application, written in JavaScript, for automatically generating template-formatted, multi-page HTML (or XML, JSON, or any other text-based) documentation from commented JavaScript source code. . Based on the JSDoc.pm project, this was renamed "Jsdoc Toolkit" during development as it grew into more than a simple version upgrade. debian/compat0000644000000000000000000000000211523634341010366 0ustar 7 debian/watch0000644000000000000000000000024611546077741010235 0ustar version=3 opts=dversionmangle=s/\+dfsg// \ http://code.google.com/p/jsdoc-toolkit/downloads/list \ http://jsdoc-toolkit.googlecode.com/files/jsdoc_toolkit-(.*)\.zip debian/copyright0000644000000000000000000011035411546073246011135 0ustar This work was packaged for Debian by: Georges Khaznadar on Mon, 07 Feb 2011 01:12:15 +0100 It was downloaded from: http://jsdoc-toolkit.googlecode.com/files/jsdoc_toolkit-2.4.0.zip Upstream Author: Michael Mathews (jsdoc-toolkit) Avi Deitcher (jsdoc-toolkit's wrapper) Copyright: Copyright (c) 2009 Michael Mathews Copyright (c) 2008-2009 Atomic Inc License: JSDoc.pm the MIT License. This project is based on the JSDoc.pm tool, created by Michael Mathews and Gabriel Reid. Complete documentation on JsDoc Toolkit can be found on the project wiki at http://code.google.com/p/jsdoc-toolkit Here is a copy of the MIT license: ----------------8<------------------------------------------ The MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ----------------8<------------------------------------------ Rhino Rhino (JavaScript in Java) is open source and licensed by Mozilla under the MPL 1.1 or later/GPL 2.0 or later licenses, the text of which is available at http://www.mozilla.org/MPL/ You can obtain the source code for Rhino from the Mozilla web site at http://www.mozilla.org/rhino/download.html here is a copy of the MPL license: ----------------8<------------------------------------------ MOZILLA PUBLIC LICENSE Version 1.1 --------------- 1. Definitions. 1.0.1. "Commercial Use" means distribution or otherwise making the Covered Code available to a third party. 1.1. "Contributor" means each entity that creates or contributes to the creation of Modifications. 1.2. "Contributor Version" means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor. 1.3. "Covered Code" means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof. 1.4. "Electronic Distribution Mechanism" means a mechanism generally accepted in the software development community for the electronic transfer of data. 1.5. "Executable" means Covered Code in any form other than Source Code. 1.6. "Initial Developer" means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A. 1.7. "Larger Work" means a work which combines Covered Code or portions thereof with code not governed by the terms of this License. 1.8. "License" means this document. 1.8.1. "Licensable" means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein. 1.9. "Modifications" means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is: A. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications. B. Any new file that contains any part of the Original Code or previous Modifications. 1.10. "Original Code" means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License. 1.10.1. "Patent Claims" means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor. 1.11. "Source Code" means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge. 1.12. "You" (or "Your") means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity. 2. Source Code License. 2.1. The Initial Developer Grant. The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims: (a) under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and (b) under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof). (c) the licenses granted in this Section 2.1(a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License. (d) Notwithstanding Section 2.1(b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices. 2.2. Contributor Grant. Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license (a) under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and (b) under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination). (c) the licenses granted in Sections 2.2(a) and 2.2(b) are effective on the date Contributor first makes Commercial Use of the Covered Code. (d) Notwithstanding Section 2.2(b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor. 3. Distribution Obligations. 3.1. Application of License. The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5. 3.2. Availability of Source Code. Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or via an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available via Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party. 3.3. Description of Modifications. You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code. 3.4. Intellectual Property Matters (a) Third Party Claims. If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained. (b) Contributor APIs. If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the LEGAL file. (c) Representations. Contributor represents that, except as disclosed pursuant to Section 3.4(a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License. 3.5. Required Notices. You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer. 3.6. Distribution of Executable Versions. You may distribute Covered Code in Executable form only if the requirements of Section 3.1-3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer. 3.7. Larger Works. You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code. 4. Inability to Comply Due to Statute or Regulation. If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the LEGAL file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it. 5. Application of this License. This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code. 6. Versions of the License. 6.1. New Versions. Netscape Communications Corporation ("Netscape") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number. 6.2. Effect of New Versions. Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License. 6.3. Derivative Works. If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL", "NPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.) 7. DISCLAIMER OF WARRANTY. COVERED CODE IS PROVIDED UNDER THIS LICENSE ON AN "AS IS" BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, WARRANTIES THAT THE COVERED CODE IS FREE OF DEFECTS, MERCHANTABLE, FIT FOR A PARTICULAR PURPOSE OR NON-INFRINGING. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE COVERED CODE IS WITH YOU. SHOULD ANY COVERED CODE PROVE DEFECTIVE IN ANY RESPECT, YOU (NOT THE INITIAL DEVELOPER OR ANY OTHER CONTRIBUTOR) ASSUME THE COST OF ANY NECESSARY SERVICING, REPAIR OR CORRECTION. THIS DISCLAIMER OF WARRANTY CONSTITUTES AN ESSENTIAL PART OF THIS LICENSE. NO USE OF ANY COVERED CODE IS AUTHORIZED HEREUNDER EXCEPT UNDER THIS DISCLAIMER. 8. TERMINATION. 8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive. 8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that: (a) such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above. (b) any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant. 8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license. 8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination. 9. LIMITATION OF LIABILITY. UNDER NO CIRCUMSTANCES AND UNDER NO LEGAL THEORY, WHETHER TORT (INCLUDING NEGLIGENCE), CONTRACT, OR OTHERWISE, SHALL YOU, THE INITIAL DEVELOPER, ANY OTHER CONTRIBUTOR, OR ANY DISTRIBUTOR OF COVERED CODE, OR ANY SUPPLIER OF ANY OF SUCH PARTIES, BE LIABLE TO ANY PERSON FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF GOODWILL, WORK STOPPAGE, COMPUTER FAILURE OR MALFUNCTION, OR ANY AND ALL OTHER COMMERCIAL DAMAGES OR LOSSES, EVEN IF SUCH PARTY SHALL HAVE BEEN INFORMED OF THE POSSIBILITY OF SUCH DAMAGES. THIS LIMITATION OF LIABILITY SHALL NOT APPLY TO LIABILITY FOR DEATH OR PERSONAL INJURY RESULTING FROM SUCH PARTY'S NEGLIGENCE TO THE EXTENT APPLICABLE LAW PROHIBITS SUCH LIMITATION. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES, SO THIS EXCLUSION AND LIMITATION MAY NOT APPLY TO YOU. 10. U.S. GOVERNMENT END USERS. The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein. 11. MISCELLANEOUS. This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License. 12. RESPONSIBILITY FOR CLAIMS. As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability. 13. MULTIPLE-LICENSED CODE. Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the NPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A. EXHIBIT A -Mozilla Public License. ``The contents of this file are subject to the Mozilla Public License Version 1.1 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.mozilla.org/MPL/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. The Original Code is ______________________________________. The Initial Developer of the Original Code is ________________________. Portions created by ______________________ are Copyright (C) ______ _______________________. All Rights Reserved. Contributor(s): ______________________________________. Alternatively, the contents of this file may be used under the terms of the _____ license (the "[___] License"), in which case the provisions of [______] License are applicable instead of those above. If you wish to allow use of your version of this file only under the terms of the [____] License and not to allow others to use your version of this file under the MPL, indicate your decision by deleting the provisions above and replace them with the notice and other provisions required by the [___] License. If you do not delete the provisions above, a recipient may use your version of this file under either the MPL or the [___] License." [NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.] ----------------8<------------------------------------------ JsDoc Toolkit is a larger work that uses the Rhino JavaScript engine but is not derived from it in any way. The Rhino library is used without modification and without any claims whatsoever. The Rhino Debugger You can obtain more information about the Rhino Debugger from the Mozilla web site at http://www.mozilla.org/rhino/debugger.html its license is MPL 1.1/GPL 2.0; see above for the text of MPL 1.1 on Debian systems, the text of the GPL-2 can be found at /usr/share/common-licenses/GPL-2 JsDoc Toolkit is a larger work that uses the Rhino Debugger but is not derived from it in any way. The Rhino Debugger is used without modification and without any claims whatsoever. JsDoc Toolkit All code specific to JsDoc Toolkit are free, open source and licensed for use under the X11/MIT License. This program is free software; you can redistribute it and/or modify it under the terms below. ----------------8<------------------------------------------ Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. ----------------8<------------------------------------------ Dumper.js Upstream Authors: Kevin Jones has authored the JavaScript library Data.Dump Gisle Aas had authored Data::Dump Gurusamy Sarathy had authored Data::Dumper Copyright: Copyright (c) 2007 Kevin Jones. Copyright (c) 1998-2000,2003-2004 Gisle Aas. Copyright (c) 1996-1998 Gurusamy Sarathy. This program is free software; you can redistribute it and/or modify it under the terms of the Perl Artistic License here is a copy of the Perl Artistic License: ----------------8<------------------------------------------ The "Artistic License" Preamble The intent of this document is to state the conditions under which a Package may be copied, such that the Copyright Holder maintains some semblance of artistic control over the development of the package, while giving the users of the package the right to use and distribute the Package in a more-or-less customary fashion, plus the right to make reasonable modifications. Definitions: "Package" refers to the collection of files distributed by the Copyright Holder, and derivatives of that collection of files created through textual modification. "Standard Version" refers to such a Package if it has not been modified, or has been modified in accordance with the wishes of the Copyright Holder as specified below. "Copyright Holder" is whoever is named in the copyright or copyrights for the package. "You" is you, if you're thinking about copying or distributing this Package. "Reasonable copying fee" is whatever you can justify on the basis of media cost, duplication charges, time of people involved, and so on. (You will not be required to justify it to the Copyright Holder, but only to the computing community at large as a market that must bear the fee.) "Freely Available" means that no fee is charged for the item itself, though there may be fees involved in handling the item. It also means that recipients of the item may redistribute it under the same conditions they received it. 1. You may make and give away verbatim copies of the source form of the Standard Version of this Package without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers. 2. You may apply bug fixes, portability fixes and other modifications derived from the Public Domain or from the Copyright Holder. A Package modified in such a way shall still be considered the Standard Version. 3. You may otherwise modify your copy of this Package in any way, provided that you insert a prominent notice in each changed file stating how and when you changed that file, and provided that you do at least ONE of the following: a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or placing the modifications on a major archive site such as uunet.uu.net, or by allowing the Copyright Holder to include your modifications in the Standard Version of the Package. b) use the modified Package only within your corporation or organization. c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided, and provide a separate manual page for each non-standard executable that clearly documents how it differs from the Standard Version. d) make other distribution arrangements with the Copyright Holder. 4. You may distribute the programs of this Package in object code or executable form, provided that you do at least ONE of the following: a) distribute a Standard Version of the executables and library files, together with instructions (in the manual page or equivalent) on where to get the Standard Version. b) accompany the distribution with the machine-readable source of the Package with your modifications. c) give non-standard executables non-standard names, and clearly document the differences in manual pages (or equivalent), together with instructions on where to get the Standard Version. d) make other distribution arrangements with the Copyright Holder. 5. You may charge a reasonable copying fee for any distribution of this Package. You may charge any fee you choose for support of this Package. You may not charge a fee for this Package itself. However, you may distribute this Package in aggregate with other (possibly commercial) programs as part of a larger (possibly commercial) software distribution provided that you do not advertise this Package as a product of your own. You may embed this Package's interpreter within an executable of yours (by linking); this shall be construed as a mere form of aggregation, provided that the complete Standard Version of the interpreter is so embedded. 6. The scripts and library files supplied as input to or produced as output from the programs of this Package do not automatically fall under the copyright of this Package, but belong to whoever generated them, and may be sold commercially, and may be aggregated with this Package. If such scripts or library files are aggregated with this Package via the so-called "undump" or "unexec" methods of producing a binary executable image, then distribution of such an image shall neither be construed as a distribution of this Package nor shall it fall under the restrictions of Paragraphs 3 and 4, provided that you do not represent such an executable image as a Standard Version of this Package. 7. C subroutines (or comparably compiled subroutines in other languages) supplied by you and linked into this Package in order to emulate subroutines and variables of the language defined by this Package shall not be considered part of this Package, but are the equivalent of input as in Paragraph 6, provided these subroutines do not change the language in any way that would cause it to fail the regression tests for the language. 8. Aggregation of this Package with a commercial distribution is always permitted provided that the use of this Package is embedded; that is, when no overt attempt is made to make this Package's interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package. 9. The name of the Copyright Holder may not be used to endorse or promote products derived from this software without specific prior written permission. 10. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE. The End ----------------8<------------------------------------------ The Debian packaging is: Copyright (C) 2011 Georges Khaznadar and is licensed under the GPL version 3, see "/usr/share/common-licenses/GPL-3". debian/source/0000755000000000000000000000000011523634341010470 5ustar debian/source/format0000644000000000000000000000001411523634341011676 0ustar 3.0 (quilt) debian/manpage.xml0000644000000000000000000002724511523765472011346 0ustar .
will be generated. You may view the manual page with: nroff -man .
| less'. A typical entry in a Makefile or Makefile.am is: DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/docbook-xsl/manpages/docbook.xsl XP = xsltproc -''-nonet -''-param man.charmap.use.subset "0" manpage.1: manpage.xml $(XP) $(DB2MAN) $< The xsltproc binary is found in the xsltproc package. The XSL files are in docbook-xsl. A description of the parameters you can use can be found in the docbook-xsl-doc-* packages. Please remember that if you create the nroff version in one of the debian/rules file targets (such as build), you will need to include xsltproc and docbook-xsl in your Build-Depends control field. Alternatively use the xmlto command/package. That will also automatically pull in xsltproc and docbook-xsl. Notes for using docbook2x: docbook2x-man does not automatically create the AUTHOR(S) and COPYRIGHT sections. In this case, please add them manually as ... . To disable the automatic creation of the AUTHOR(S) and COPYRIGHT sections read /usr/share/doc/docbook-xsl/doc/manpages/authors.html. This file can be found in the docbook-xsl-doc-html package. Validation can be done using: `xmllint -''-noout -''-valid manpage.xml` General documentation about man-pages and man-page-formatting: man(1), man(7), http://www.tldp.org/HOWTO/Man-Page/ --> ]> &dhtitle; &dhpackage; &dhfirstname; &dhsurname; Wrote this manpage for the Debian system.
&dhemail;
2011 &dhusername; This manual page was written for the Debian system (and may be used by others). Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or (at your option) any later version published by the Free Software Foundation. On Debian systems, the complete text of the GNU General Public License can be found in /usr/share/common-licenses/GPL-2. &dhucpackage; &dhsection; jsdoc automatic generator for HTML documentation of Javascript sources jsdoc jsdoc DESCRIPTION This manual page documents briefly the jsdoc command. jsdoc is application, written in JavaScript, for automatically generating template-formatted, multi-page HTML (or XML, JSON, or any other text-based) documentation from commented JavaScript source code. OPTIONS The program follows the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. For a complete description, see the info 1 files. Include all functions, even undocumented ones. Load a configuration file. Output to this directory (required parameter). Multiple. Define a variable, available in JsDoc as JSDOC.opt.D.myVar. Use this encoding to read and write files. Multiple. Exclude files based on the supplied regex. Show this message and exit. Don't warn about symbols being documented more than once. Ignore all code, only document comments with @name tags. Print log messages to a file (defaults to stdout). Include symbols tagged as private, underscored and inner symbols. Do not output any messages, not even warnings. Descend into src directories. Suppress source code output. Use Secure Modules mode to parse source code. Use this template to format the output. Run all unit tests and exit. Force file names to be unique, but not based on symbol names. Provide verbose feedback about what is happening. Scan source files with the given extension/s (defaults to js). BUGS The following bugs are known bugs: Does not support spaces in arguments The wrapper jsdoc is not immune to spaces in filenames, either escaped or not. debian/README.source0000644000000000000000000000055111523647731011357 0ustar jsdoc-toolkit for Debian ------------------------ This source is uncompressed from http://jsdoc-toolkit.googlecode.com/files/jsdoc_toolkit-(.*)\.zip the upper directory is renamed to jsdoc-toolkit-\1 The modifications are made with patches managed by quilt (see: "man quilt") -- Georges Khaznadar , Mon, 7 Feb 2011 02:50:17 +0100 debian/changelog0000644000000000000000000000357412103533054011045 0ustar jsdoc-toolkit (2.4.0+dfsg-6) unstable; urgency=low * fixed the DEBEMAIL's change, which was not finised in the previous release; Closes: #699633 -- Georges Khaznadar Sun, 03 Feb 2013 19:37:08 +0100 jsdoc-toolkit (2.4.0+dfsg-5) unstable; urgency=low * changed my DEBEMAIL * added the clause Closes: #684012, which was forgot last time -- Georges Khaznadar Sat, 02 Feb 2013 15:56:07 +0100 jsdoc-toolkit (2.4.0+dfsg-4) unstable; urgency=low * applied James Page's patch... Transition to using default java implementation: - d/control: BD switched from openjdk-6-jdk -> default-jdk. - d/rules: Set source/target = 1.5 to ensure backwards compatible bytecode is built. * bumped Standards-Version to 3.9.3 -- Georges Khaznadar Sun, 19 Aug 2012 08:52:43 +0200 jsdoc-toolkit (2.4.0+dfsg-3) unstable; urgency=low * added a few ";" chars ending JavaScript lines; fixes a recent picky behavior in rhino. -- Georges Khaznadar Sat, 16 Jul 2011 16:55:55 +0200 jsdoc-toolkit (2.4.0+dfsg-2) unstable; urgency=low * fixed the debian/watch file * bumped Standards-Version to 3.9.2 * Closes: #559963 (already fixed RFP) -- Georges Khaznadar Sat, 16 Jul 2011 16:33:56 +0200 jsdoc-toolkit (2.4.0+dfsg-1) unstable; urgency=low * fixed license issues: added a copy of the Perl Artistic License for Dumper.js * removed the .jar from the source package. * New upload (Closes: #612243) -- Georges Khaznadar Sun, 03 Apr 2011 15:37:29 +0200 jsdoc-toolkit (2.4.0-1) unstable; urgency=low * Initial release (Closes: #612243) * made a convenient wrapper and written its manpage * changed the java archive to take in account an absolute path tho Rhino -- Georges Khaznadar Mon, 07 Feb 2011 10:31:58 +0100 debian/jsdoc-toolkit.dirs0000644000000000000000000000005411523660705012642 0ustar usr/bin usr/share/jsdoc-toolkit/java/classesdebian/rules0000755000000000000000000000242112014106463010242 0ustar #!/usr/bin/make -f # -*- makefile -*- # Sample debian/rules that uses debhelper. # This file was originally written by Joey Hess and Craig Small. # As a special exception, when this file is copied by dh-make into a # dh-make output file, you may use that output file without restriction. # This special exception was added by Craig Small in version 0.37 of dh-make. # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 %: dh $@ DB2MAN = /usr/share/sgml/docbook/stylesheet/xsl/docbook-xsl/manpages/docbook.xsl XP = xsltproc --nonet --param man.charmap.use.subset "0" PACKAGE = jsdoc-toolkit DESTDIR = $(CURDIR)/debian/$(PACKAGE) override_dh_auto_clean: find . -name "*.jar" -exec rm {} \; find . -name "*.class" -exec rm {} \; dh_auto_clean override_dh_auto_build: cd jsdoc-toolkit/java; ant -Dant.build.javac.source=1.5 -Dant.build.javac.target=1.5 clean-build cd debian; $(XP) $(DB2MAN) manpage.xml dh_auto_build override_dh_install: dh_install find $(DESTDIR)/usr/share/jsdoc-toolkit -name "*.js" -exec chmod 644 {} \; rm -f $(DESTDIR)/usr/share/jsdoc-toolkit/app/test/prototype.js ln -s /usr/share/javascript/prototype/prototype.js \ $(DESTDIR)/usr/share/jsdoc-toolkit/app/test cp $(DESTDIR)/usr/share/java/jsrun.jar \ $(DESTDIR)/usr/share/jsdoc-toolkit/