Skip to content
Commits on Source (9)
Expand all Show whitespace changes
Inline Side-by-side
Makefile
View file @ 0bb64406
...@@ -5,73 +5,47 @@ ...@@ -5,73 +5,47 @@
# $< First prerequisity # $< First prerequisity
# $@ Target # $@ Target
# Some default variables # Now we only build HTML
DOC = usr/share/doc # Let's just use simple xslt
DVIPS=dvips # If PDF and epub are needed, we can take script from debian-reference
PUBLISHDIR=$(DESTDIR)/$(DOC)/java-policy
#DSLF=work.dsl # version of this Debian package (debian/changelog)
#DSL=-d $(DSLF) DEBVERSION ?= $(shell { dpkg-parsechangelog -SVersion || echo "vcs-0.0" ; })
# Default language to use # short date of this Debian package (debian/changelog)
LANGUAGE= DEBDATE ?= $(shell { date +'%Y-%m-%d' -d"`dpkg-parsechangelog -SDate`" || date +'(No changelog) %Y-%m-%d' ; })
LANG=C
LC_CTYPE=C XSLTPROCH := xsltproc --xinclude $(CURDIR)/style-html.xsl
XSLTPROCT := xsltproc --xinclude $(CURDIR)/style-txt.xsl
all: debian-java-policy/index.html debian-java-faq/index.html \
debian-java-policy.txt debian-java-faq.txt
binary: all
%/index.html: %.xml
mkdir -p $*
cp debian-java.css $*/
cd $* ; \
sed \
-e "s/@@@debversion@@@/$(DEBVERSION)/g" \
-e "s/@@@debdate@@@/$(DEBDATE)/g" \
< $(CURDIR)/$< | \
$(XSLTPROCH) -
%.txt: %.xml
sed \
-e "s/@@@debversion@@@/$(DEBVERSION)/g" \
-e "s/@@@debdate@@@/$(DEBDATE)/g" \
< $< | \
$(XSLTPROCT) - | \
LC_ALL=en_US.UTF-8 w3m -o display_charset=UTF-8 -cols 70 -dump -no-graph -T text/html \
> $@
distclean: clean
clean:
-rm -rf debian-java-policy
-rm -rf debian-java-faq
-rm -f debian-java-policy.txt
-rm -f debian-java-faq.txt
all: debian-java-policy debian-java-faq-gen
# Policy part
MAKEOUT=policy.txt policy.ps
OUTPUTS=$(MAKEOUT) policy.xml
MAKEDEP=$(MAKEOUT) policy.html
debian-java-policy: $(MAKEDEP)
update: debian-java-faq-update
policy.tex: policy.xml
jw $(DCL) -b tex $(DSL) policy.xml
policy.dvi: policy.xml
jw $(DCL) -b dvi $(DSL) policy.xml
policy.ps: policy.dvi
$(DVIPS) -f $< > $@
policy.html: debian-java-policy/index.html
debian-java-policy/index.html: policy.xml
# docbook and dsl file needs to be in that dir for things to work.
# The png file is copied there so it can be referenced in a proper way.
#
# This is no longer true.
mkdir -p debian-java-policy
jw -b html $(DSL) -o debian-java-policy $<
# To make that file the intdex.
(cd debian-java-policy; rm -f $^)
policy.txt: policy.xml
jw -b txt $(DSL) $<
install: debian-java-policy-install debian-java-faq-install
debian-java-policy-install:
mkdir -p $(PUBLISHDIR)
install -m 0444 $(OUTPUTS) $(PUBLISHDIR)
cp -a debian-java-policy $(PUBLISHDIR)
clean: faq
-rm -Rf debian-java-policy
-rm -Rf policy.html
-rm -f $(MAKEOUT)
-rm -f policy.dvi
(cd $<; make clean)
debian-java-faq-gen: faq
(cd $<; make debian-java-faq.html/index.html)
# Change the publish dir if you want to send it to a new package.
debian-java-faq-install: faq debian-java-faq-gen
(cd $<; make publish PUBLISHDIR=$(PUBLISHDIR))
debian-java-faq-update: faq
svn export svn://svn.debian.org/svn/ddp/manuals/trunk/java-faq/ faq-update/
cp faq-update/* $</
rm -fr faq-update/
debian-java-faq.xml 0 → 100644
View file @ 0bb64406
This diff is collapsed.
policy.xml → debian-java-policy.xml
View file @ 0bb64406
<?xml version='1.0'?> <?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN" <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
"/usr/share/sgml/docbook/dtd/4.1/docbook.dtd" "/usr/share/sgml/docbook/dtd/4.1/docbook.dtd"
[ [
...@@ -31,7 +31,6 @@ ...@@ -31,7 +31,6 @@
<book> <book>
<bookinfo> <bookinfo>
<title>Debian policy for Java</title> <title>Debian policy for Java</title>
<edition>$Revision:$ $Date:$</edition>
<authorgroup> <authorgroup>
<author> <author>
<surname>Thykier</surname> <surname>Thykier</surname>
...@@ -103,6 +102,8 @@ ...@@ -103,6 +102,8 @@
This policy is published under the GNU GPL v2 or later license. This policy is published under the GNU GPL v2 or later license.
</para> </para>
</abstract> </abstract>
<releaseinfo>Release: @@@debversion@@@</releaseinfo>
<pubdate>Date: @@@debdate@@@</pubdate>
</bookinfo> </bookinfo>
<chapter id="background"> <chapter id="background">
......
debian-java.css 0 → 100644
View file @ 0bb64406
/* Cascading stylesheet for the Debian Installer internals talk */
/* Use grey background for examples */
pre.screen {
background-color : #E0E0E0;
}
debian/changelog
View file @ 0bb64406
java-policy (0.56) UNRELEASED; urgency=medium java-policy (0.56) unstable; urgency=medium
* Team upload. * Team upload.
[ Emmanuel Bourg ]
* Changed the maintainer back from 'Debian Java Maintainers' * Changed the maintainer back from 'Debian Java Maintainers'
to 'Debian Java Mailing List' to 'Debian Java Mailing List'
* Standards-Version updated to 4.0.0
* Switch to debhelper level 10
* Use a secure Vcs-Git URL
-- Emmanuel Bourg <ebourg@apache.org> Thu, 29 Jun 2017 17:30:28 +0200 [ shirish शिरीष ]
* FAQ: Updates such as OpenJDK 7 and 8.
* Removed $ID and add pointer to https://java.debian.net/
[ Osamu Aoki ]
* Switch to debhelper level 11
* Standards-Version updated to 4.2.1
* Use new Vcs-Git/Vcs-web URLs at salsa.debian.org
* FAQ: Conversion to DocBook XML 4.5
* Clean up build script to use XSLT instead of old dsssl.
-- Osamu Aoki <osamu@debian.org> Mon, 03 Sep 2018 23:18:55 +0900
java-policy (0.55) unstable; urgency=medium java-policy (0.55) unstable; urgency=medium
......
debian/control
View file @ 0bb64406
...@@ -3,10 +3,10 @@ Section: java ...@@ -3,10 +3,10 @@ Section: java
Priority: optional Priority: optional
Maintainer: Debian Java Mailing List <debian-java@lists.debian.org> Maintainer: Debian Java Mailing List <debian-java@lists.debian.org>
Uploaders: Emmanuel Bourg <ebourg@apache.org> Uploaders: Emmanuel Bourg <ebourg@apache.org>
Build-Depends: debhelper (>= 10), debiandoc-sgml, docbook-utils, docbook-xml Build-Depends: debhelper (>= 11~), docbook-xml, docbook-xsl, w3m, xsltproc,
Standards-Version: 4.0.0 Standards-Version: 4.2.1
Vcs-Git: https://anonscm.debian.org/git/pkg-java/java-common.git Vcs-Git: https://salsa.debian.org/java-team/java-policy.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-java/java-common.git Vcs-Browser: https://salsa.debian.org/java-team/java-policy
Homepage: https://wiki.debian.org/Java/ Homepage: https://wiki.debian.org/Java/
Package: java-policy Package: java-policy
......
debian/install 0 → 100644
View file @ 0bb64406
debian-java-policy/ usr/share/doc/java-policy/
debian-java-faq/ usr/share/doc/java-policy/
debian-java-policy.txt usr/share/doc/java-policy/
debian-java-faq.txt usr/share/doc/java-policy/
debian/java-policy.doc-base.faq
View file @ 0bb64406
...@@ -8,6 +8,9 @@ Abstract: The Debian Java FAQ provide answers to many ...@@ -8,6 +8,9 @@ Abstract: The Debian Java FAQ provide answers to many
libraries and applications as well as legal issues. libraries and applications as well as legal issues.
Section: Debian Section: Debian
Format: text
Files: /usr/share/doc/java-policy/debian-java-faq.txt.gz
Format: HTML Format: HTML
Index: /usr/share/doc/java-policy/debian-java-faq/index.html Index: /usr/share/doc/java-policy/debian-java-faq/index.html
Files: /usr/share/doc/java-policy/debian-java-faq/*.html Files: /usr/share/doc/java-policy/debian-java-faq/*.html
debian/links 0 → 100644
View file @ 0bb64406
usr/share/doc/java-policy/debian-java-policy.txt.gz usr/share/doc/java-policy/policy.txt.gz
faq/Makefile deleted 100644 → 0
View file @ 97ffdf26
# Makefile for a manual in the Debian Documentation Project manuals.sgml
# tree.
# The directory in which this makefile resides must also contain a file
# called <directoryname>.sgml, which is the top-level file for the manual
# in this directory.
# What is the current manual's name
#MANUAL := $(shell basename $(shell pwd))
MANUAL := debian-java-faq
# Where are we publishing to?
# (this can be overriden by a higher level makefile)
PUBLISHDIR := /org/www.debian.org/www/doc/manuals
# What do we want by default?
all: publish
# This target installs the generated HTML in the published directory.
publish: $(MANUAL).html/index.html
# fail if there is no PUBLISHDIR
[ -d $(PUBLISHDIR) ] || exit 1
rm -f $(PUBLISHDIR)/$(MANUAL)/*.html
install -d -m 755 $(PUBLISHDIR)/$(MANUAL)
install -m 644 --preserve-timestamps $(MANUAL).html/*.html \
$(PUBLISHDIR)/$(MANUAL)/
generate: $(MANUAL).html/index.html
$(MANUAL).html/index.html: $(wildcard *.sgml)
debiandoc2html $(MANUAL).sgml
# ensure our SGML is valid
# (add this to $(MANUAL).html rule to prevent building if not)
validate:
nsgmls -gues $(MANUAL).sgml
clean:
rm -rf $(MANUAL).html
distclean: clean
.PHONY: all publish clean distclean validate
faq/debian-java-faq.sgml deleted 100644 → 0
View file @ 97ffdf26
<!doctype debiandoc system>
<book>
<titlepag>
<title>Debian Java FAQ.</title>
<author>
<name>Torsten Werner</name>
<email>twerner@debian.org</email>
</author>
<author>
<name>Niels Thykier</name>
<email>niels@thykier.net</email>
</author>
<author>
<name>Javier Fernández-Sanguino Peña</name>
<email>jfs@debian.org</email>
</author>
<author>
<name>Sylvestre Ledru</name>
<email>sylvestre@debian.org</email>
</author>
<version>$Revision: 7831 $, $Date: 2013-06-05 21:17:15 +0100 $
<abstract>
Answers to Frequently Asked Questions on Debian and Java
(Note: some information is not up-to-date). Any changes/corrections to this
FAQ are appreciated. Please send them to the Debian Bug Tracking System as
described in <ref id="bugs">.
</abstract>
<copyright>
This document may be freely redistributed or modified in any form
provided your changes are clearly documented.
This document may be redistributed for fee or free, and may be modified
(including translation from one type of media or file format to another
or from one spoken language to another) provided that all changes
from the original are clearly marked as such.
</copyright>
</titlepag>
<toc>
<chapt>Introduction
<p>
<sect>Introduction to this FAQ
<P>This FAQ was started by Javier Fernández-Sanguino who on
February 1st, 2000 was enough to send a message to the debian-java
mailing list with the subject "How about a Debian-Java-FAQ?". Of
course, since "every idea is a responsibility" he had to do this himself
looking through the three month-long archive of the newborn mailing list.
<p>The purpose of this FAQ is to be a place to look for all kinds of
questions a developer or user might have regarding Java as far as Debian
is concerned. It includes license issues, development packages available,
and programs related to building a Free Software Java environment.
<p>Thanks go to all the (many) contributors from the debian-java mailing list,
who have made this document possible. Without their knowledge this
FAQ would not be at all possible since I only have a vague knowledge
of what they're talking about when I browse the list.
<p>Special thanks go to Paul Reavis, whose previous Debian-JDK
informational page I used to add more information, and who made useful
suggestions to this document. Also to Peter Moulder who revised
thoroughly the FAQ and provided many suggestions, to Juergen
Kreileder, maintainer of Blackdown's debian packages who pointed out
some mistakes, and to Egon Willighagen, who has provided quite a lot
of proper patches to update its content.
<p>This document does not address issues with other Linux
distributions, or with non-Debian-specific problems.
<sect>Location of this FAQ
<p>This FAQ is published under the Debian Documentation Project
at <url id="http://www.debian.org/doc/manuals/debian-java-faq/">.
The <package>java-common</package> (available at
<url id="http://packages.debian.org/java-common">) provides an
HTML version for offline reading. The package version does not provide Text and
PDF versions currently (if you want them please submit a bug
'wishlist' to the package). Also, the web version might be more up-to-date
than the package's offline version.
<sect id="bugs">Sending bugs on this FAQ
<P>Please note that this FAQ is still outdated but gets updated step by step.
<p> Please file bug reports against the java-common package if you find errors
or have suggestions on how to improve this document. However, make sure you
have read the latest online version of the english text available at <url
id="http://www.debian.org/doc/manuals/debian-java-faq/index.html"> before
filing a bug report. Translations, if available, and the offline version in
the java-common package might be out of date.
<sect>What is Java?
<p>
Java is a programming language originally developed by James Gosling at
Sun Microsystems (which is now a subsidiary of Oracle Corporation) and
released in 1995 as a core component of Sun Microsystems' Java platform.
Since May 2007, Sun/Oracle with some partners like Red Hat provide a free
implementation released under the GNU GPL called OpenJDK.
More information can be found at <url
id="http://en.wikipedia.org/wiki/Java_%28programming_language%29"
name="Wikipedia">.
<sect>Where can I ask questions about Java on Debian?
<p>The appropriate place to ask such questions is <email>debian-java
at lists.debian.org</email>. You can subscribe at the <url
id="http://lists.debian.org/debian-java/" name="Debian Mailing Lists"> page.
<sect id="moreinfo">Complementary information
<p>Users might want to access some online sources to complement the
information available in this FAQ which might be, sometimes, too out
of date. The main source of information is the
<url id="http://wiki.debian.org/Java" name="Java entry"> at the Debian's wiki.
<p>Since Ubuntu is based on Debian, some users might find it helpful
to check the tips on <url id="https://help.ubuntu.com/community/Java"
name="Installing Java"> on Ubuntu's wiki.
<sect id="pending">Uncovered issues
<p>This FAQ does not describe some issues due to lack of time and/or
information. If you are able to help in any of these, please, provide
them to the documentation maintainer:
<list>
<item>Information on how to setup a fully working Servlet engine (Application
Server) using Apache and Tomcat or information on how to setup non-free
application servers (such as WebSphere) in Debian.
<item>Specific information targeted for non-i386 users (PowerPC users and AMD64 users), some can be found in Ubuntu's wiki.
</list>
<chapt>Java Development
<p>
<sect>What full-fledged Java development platforms are available in Debian?
<p> If you are looking for an integrated, java virtual machine,
compiler and runtime environment Debian does provide them. Of course
that would depend on the Debian GNU/Linux version you are using,
generally speaking they would be:
<list>
<item>Sun's OpenJDK 6, available since the Debian 5.0 <em>Lenny</em>
release in the <em>main</em> section.
<item>Oracle's OpenJDK 7, available since the Debian 7.0 <em>Wheezy</em>
release in the <em>main</em> section.
<item>The combination GCJ, GIJ, and Classpath in the <em>main</em> section.
</list>
<p>It is recommended to install one of the default-jdk or default-jre meta
packages which either installs OpenJDK or GCJ depending on the architecture and
Debian version.
<sect id="free">What free platforms are there and how can I contribute?
<p>
Please help one of the Free Java implementations if you want to use Java
in Debian. There are a lot of projects that you can choose from:
<list>
<item>openjdk: <url id="http://openjdk.java.net/"></item>
<item>gcj and libgcj: <url id="http://gcc.gnu.org/java/"></item>
<item>Classpath <url id="http://www.classpath.org">. Most of the
Standard classes for Java 1.2 (except Swing and RMI) are implemented by
the ClassPath project, it tries to build an alternative to jdk's 1.2
core classes. (NB: This was removed from Squeeze)</item>
<item>Mauve <url
id="http://sources.redhat.com/mauve/"> is a free suite to test if
these tools are 'compliant'.</item>
</list>
<p>Most free Java development is grouped under the <url
id="http://www.gnu.org/software/java/" name="Free Java
Project">.
<sect id="license-concerns">Questions on platforms and license concerns
<sect1 id="java6">Java 6 and 7
<p>There are binary packages available for the Java 6 and Java 7 platforms
since the Debian 7.0 ('wheezy') release.
Once this is done and you have updated your package database. You can either
install the Java development kit:
<example>
apt-get install openjdk-6-jdk
</example>
or the Java runtime environment:
<example>
apt-get install openjdk-6-jre
</example>
<p>Similarly, you can install the Java 7 development kit:
<example>
apt-get install openjdk-7-jdk
</example>
or the Java 7 runtime environment:
<example>
apt-get install openjdk-7-jre
</example>
<p>You might want to update the alternatives system to have Sun's tools as the
default:
<example>
update-java-alternatives -s java-1.6.0-openjdk-amd64
</example>
Or for java 7:
<example>
update-java-alternatives -s java-1.7.0-openjdk-amd64
</example>
<sect1 id="openjdk">Oracle proprietary JVM
<p>Since the version 7 of the OpenJDK, the proprietary JVM developments are done on the OpenJDK. That means that the OpenJDK is strongly tested and high quality.
<p>However, some users might want to use the Oracle JVM for the proprietary extensions (for example: the browser plugin). For such need, Debian provides a tool called <url id="http://packages.debian.org/sid/java-package" name="java-package">. The program make-jpkg will take an upstream archive and convert it to a Debian package. For example:
<example>
make-jpkg jdk-6u31-linux-x64.bin
</example>
<p>For more information see <url id="http://www.oracle.com/technetwork/java/index.html" name="Oracle Technology Network Java">.
<sect>Making Debian packages for Java programs.
<sect1>Can the package go into main?
<p>Yes, <em>but only if</em> it can be build and run with Java programs/tools
in main, and if it has a Debian compliant open source license.
If it needs programs from contrib or non-free, then is <em>must</em>
go into contrib or non-free, depending on the license of the program itself.
<sect1>Is there a good example Debian package?
<p>There are many Debian packages of both Java applications and libraries.
These may serve as an good starting point, as it can serve as an example
for making a new Debian package.
<p>A good start would be to check out the pkg-java project on
Alioth: <url id="http://pkg-java.alioth.debian.org/">.
<p>Note that there are many ways to make a Debian package, making use
of Ant or Makefiles does not really matter.
But, some tips for good practice are given on the pkg-java page:
<url id="http://pkg-java.alioth.debian.org/developers.html#rules"> and
<url id="http://pkg-java.alioth.debian.org/building.html">.
<sect1>What tools are available to make maintaining a Java packages easier?
<p>Both cdbs and debhelper (dh7) have support for ant scripts. There
are also a number of specialized tools or build helpers. Have a look
at <package>javahelper</package>
or <package>maven-debian-helper</package>. <package>gcj-jdk</package>
also has a dh_javadoc tool.</p>
<sect1>Linking package Javadoc to system javadoc.
<p>The java-policy mandates that documentation must be linked with the
javadoc installed on the system. This can be done by passing javadoc
the "-link" argument or by using the &lt;link&gt; tag in ant. An
example:
<example>
# command line example of linking against system doc.
javadoc -link /usr/share/doc/default-jdk-doc/api [other arguments]
&lt;!-- Ant example of linking against system doc --&gt;
&lt;javadoc [attributes]&gt;
&lt;link href="/usr/share/doc/default-jdk-doc/api/" /&gt;
[other tags]
&lt;/javadoc&gt;
</example>
</p>
<p>The documentation must be installed at the time the linking is
done; so in the example cases above the package would need a
Build-Depends or a Build-Depends-Indep on
<package>default-jdk-doc</package>.
</p>
<p>
Here is a short list of packages that can be used for reference:
<list>
<item><package>commons-jci</package></item>
<item><package>ow-util-ant-tasks</package></item>
<item><package>libhamcrest-java</package></item>
<item><package>libfreemarker-java</package></item>
</list>
</p>
<chapt>Managing Java (for users and administrators)
<p>
By default Java programs shipped with Debian will use the java
in PATH. Some of them may respect the JAVA_HOME variable
(usually only if upstream supports this) or have command line
arguments to select a different java implementation.
</p>
<p>
Unfortunately not all java implementations work as well as others.
So some times it may be necessary to change the current java and
Debian provides an easy way to change the default java in PATH by
using update-java-alternatives (from the <package>java-common
</package>). Some examples of how to do this are:
</p>
<p>
<example>
# List available java implementations
$ update-java-alternatives --list
# Use openjdk-6
$ update-java-alternatives --set java-6-openjdk
# Use the non-free sun java.
$ update-java-alternatives --set java-6-sun
# Use the non-free sun java only for the web plugin
$ update-java-alternatives --plugin --set java-6-sun
</example>
</p>
<p>
For more information, please read the manpage (or the --help
output) of update-java-alternatives. Also please note that
update-java-alternatives is a frontend for update-alternatives.
</p>
<chapt>Java Virtual Machines (JVM)
<p>
<sect>What JVMs are available in Debian?
<p>The following JVMs are currently available in Debian Wheezy:
<list>
<item><package>openjdk-6-jre</package></item>
<item><package>openjdk-7-jre</package></item>
<item><package>gcj-4.7-jre</package></item>
</list>
</p>
<p>The following lists JVMs available in Debian 6.0 release ('Squeeze'):
<list>
<item><package>openjdk-6-jre</package></item>
<item><package>sun-java6-jre</package> (non-free)</item>
<item><package>gcj-4.4-jre</package></item>
</list>
<p>
<sect>What Java Compilers are available in Debian?
<p>
<list>
<item><package>openjdk-6-jdk</package></item>
<item><package>openjdk-7-jdk</package></item>
<item><package>gcj</package>. Compiles Java source to native code,
also source to bytecode, or bytecode to native code. Please note that the
support of the Java language is not completed.</item>
</list>
</p>
<sect>What API do these JVMs provide?
<p>Note that providing an API does not mean that everything is
implemented, and certainly not implemented correctly.
<sect>Are there known problems?
<p>Yes, there are. Some of these are reported as Debian bugs. You can
look up the bugs for a specific Debian package at the <url
id="http://www.debian.org/Bugs/" name="Debian Bug Tracking System">. As
a quick link, here are some packages:
<list>
<item><url id="http://bugs.debian.org/java-common" name="java-common"></item>
<item><url id="http://bugs.debian.org/src:openjdk-6" name="openjdk-6"></item>
<item><url id="http://bugs.debian.org/src:openjdk-7" name="openjdk-7"></item>
<item><url id="http://bugs.debian.org/src:gcj-4.7" name="gcj-4.7"></item>
</list>
<p>As common within the Debian project, the developers would
appreciate good bug reports on found problems. These include the good
description of the problem, the command that gives the problem, the
errors given when running the command, and any other information that
might be relevant. A good tool to report bugs is
<package>reportbug</package>.
<sect>How can I use the proprietary version of the JDK/JRE from Oracle as a Debian package?
<p>
The package <url id="http://packages.debian.org/wheezy/java-package/" name="java-package"> provides an easy way to convert an upstream installer into a Debian package. It should be as easy as:
<example>make-jpkg ~/Downloads/jdk-6u31-linux-x64.bin
</example>
<p>For more information, see this <url id="http://sylvestre.ledru.info/blog/2012/02/29/java_package_replacement_of_sun_java6" name="Blog article">
<sect>Do I need a JVM to run a Java program in Debian?
<p>
No, you can try to run the applications without a jvm by compiling
the source code to native code is. However, the usage of the OpenJDK is recommended. For example, gcj does not provide any support of Swing (the Java GUI API).
<sect1>How do I compile to native code?
<p>You might be able to use <prgn>gcj</prgn> to compile the program.
And use <prgn>gcj</prgn> to convert bytecode to native code. The entire
software chain is free.
<chapt id="browser-java">Java Plugins for Browsers
<p>
<list>
<item>You can install the package icedtea-6-plugin or icedtea-7-plugin in <em>wheezy</em></item>
</list>
<chapt>Java Servlets
<p>
<sect>How can I make Java servlets work?
<p>You can use:
<list>
<item>Apache <package>tomcat6</package> from <url id="http://tomcat.apache.org">.
<item>Eclipse <package>jetty</package> from <url id="http://www.eclipse.org/jetty/">.
</list>
<chapt>Java Policy
<p>
<sect>Is there a Java policy for Debian?
<p>
It is still in the works. The current policy addresses <em>some</em>
of the problems. It has not been officially released. You can find
it at <url id="http://www.debian.org/doc/packaging-manuals/java-policy/">.
The Java Policy can also be found in the <package>java-common</package>
package.
<sect>Are there holes in the Java Policy?
<p>Yes, some until under discussion. Please check out the
<url id="http://bugs.debian.org/java-common" name="bugs against
the java-common package">. Thus it is <em>very</em> inconvenient to
use several compilers of virtual machines since there is not one
CLASSPATH setting for all of them.
<chapt>Other Java alternatives for Debian
<p>If the Java packages provided in Debian are not sufficient for your
needs you might need to take a look at other alternatives. Please understand
that these alternatives are not supported by the Debian project directly,
you might get help, however, from the debian-java mailing list if you
encounter issues with them.
<P>Some of the alternatives presented use Debian packages which is
convenient, since the user/administrator does not need to care on installation
issues. However, mixing packages that come from a source which is not
the Debian project might cause conflicts with your installation some times.
Of course, Debian tries to integrate as many free software efforts as
possible, so some of the alternatives described below might (if license
permits) be included in Debian in the near future.
<sect>Java programs not yet available on Debian
<p>
The following are programs that have not yet been packaged for Debian
nor is there an installer. There are quite a lot Java programs out
there.
<p>A list of missing packages is maintained on the
<url id="http://wiki.debian.org/Java/RequestedPackages" name="Debian Wiki - Java Packaging Wishlist">.
</book>
html.dsl deleted 100644 → 0
View file @ 97ffdf26
<!--
html.dsl - stylesheets for HTML output.
Stolen from SGMLtools
-->
<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
<!ENTITY docbook.dsl PUBLIC "-//Norman Walsh//DOCUMENT DocBook HTML Stylesheet//EN" CDATA dsssl>
]>
<style-sheet>
<style-specification id="html" use="docbook">
<style-specification-body>
(define %html-ext% ".html")
(define %root-filename% "policy")
(define %generate-article-toc% #t)
(define %generate-article-titlepage% #t)
(define %use-id-as-filename% #t)
; (define %gentext-nav-use-tables% #f)
;; Add other customization here
</style-specification-body>
</style-specification>
<external-specification id="docbook" document="docbook.dsl">
</style-sheet>
style-html.xsl 0 → 100644
View file @ 0bb64406
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<!-- Import our base stylesheet -->
<xsl:import href="file:///usr/share/xml/docbook/stylesheet/docbook-xsl/xhtml-1_1/chunk.xsl"/>
<!-- Since I use xsltproc (not saxon), this is workaround to ensure UTF-8 -->
<xsl:template xmlns="http://www.w3.org/1999/xhtml" name="head.content.generator">
<xsl:param name="node" select="."/>
<meta name="generator" content="DocBook {$DistroTitle} V{$VERSION}"/>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
</xsl:template>
<xsl:template name="generate.html.title"/>
<!-- We don't want title in HTML -->
<xsl:param name="generate.meta.abstract" select="0"/>
<xsl:param name="html.stylesheet">debian-java.css</xsl:param>
<xsl:param name="root.filename">index</xsl:param>
<!-- I hate when the first subsection is on the same page as content -->
<xsl:param name="chunk.first.sections" select="0"/>
<xsl:param name="chunk.section.depth" select="0"/>
<xsl:param name="chunker.output.indent" select="'yes'"/>
<!-- Do we want fancy icons around note, warning, etc.? -->
<xsl:param name="admon.graphics" select="1"/>
<!-- Do we want fancy icons instead of Next, Prev, Up, Home? -->
<xsl:param name="navig.graphics" select="1"/>
<xsl:param name="navig.graphics.extension">.png</xsl:param>
<xsl:param name="toc.section.depth">4</xsl:param>
<xsl:param name="section.label.includes.component.label" select="1"/>
<xsl:param name="section.autolabel" select="1"/>
</xsl:stylesheet>
style-txt.xsl 0 → 100644
View file @ 0bb64406
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<!-- Import our base stylesheet -->
<xsl:import href="file:///usr/share/xml/docbook/stylesheet/docbook-xsl/xhtml-1_1/docbook.xsl"/>
<!-- parameters for optimal text output -->
<xsl:param name="callout.graphics" select="0"/>
<xsl:param name="callout.unicode" select="0"/>
<xsl:param name="section.autolabel" select="1"/>
<xsl:param name="section.label.includes.component.label" select="1"/>
<!-- just title and no toc for appendix chapter -->
<xsl:param name="generate.toc">
appendix title
article/appendix nop
article toc,title
book toc,title,figure,table,example,equation
chapter title
part toc,title
preface toc,title
qandadiv toc
qandaset toc
reference toc,title
section toc
set toc,title
</xsl:param>
<!-- centering and aligning title elements -->
<xsl:template match="/*/title[position()=1]" mode="titlepage.mode">
<br/>
<center>
<xsl:apply-imports/>
</center>
<br/>
<hr/> <!-- no underline, but at least something -->
</xsl:template>
<xsl:template match="author|editor" mode="titlepage.mode">
<center>
<xsl:apply-imports/>
</center>
</xsl:template>
<xsl:template match="releaseinfo" mode="titlepage.mode">
<center>
<xsl:apply-imports/>
</center>
<hr/>
</xsl:template>
<!-- dirty hack to get a left margin for paragraphs etc. -->
<xsl:template match="legalnotice/*
|chapter/*[not(name(.)='section') and not(name(.)='title')]
|section/*[not(name(.)='section') and not(name(.)='title')]
|appendix/*[not(name(.)='section') and not(name(.)='title')]
|footnote/*">
<xsl:copy><table><tr><td>&#xa0;&#xa0;&#xa0;</td><td>
<xsl:apply-imports/>
</td></tr></table></xsl:copy>
</xsl:template>
<!-- skip URLs if it has something to print -->
<xsl:template match="ulink[.!='']">
<xsl:copy-of select="."/>
</xsl:template>
<!-- print URLs if nothing to print -->
<xsl:template match="ulink[.='']">
<xsl:value-of select="@url"/>
</xsl:template>
<!-- make clear where notes etc. begin and end -->
<xsl:template match="caution|important|note|tip|warning">
<table width="80%" border="1">
<colgroup>
<col align="justify"/>
</colgroup>
<tbody>
<tr>
<td align="justify">
<xsl:apply-imports/>
</td>
</tr>
</tbody>
</table>
</xsl:template>
</xsl:stylesheet>