I had a quick look at ice4j and the Debian java policies
I'd be happy to have a go at packaging ice4j because I already use it
and I am familiar with it. I won't be able to do it immediately though
because of other time commitments, but when I am able to look at it, it
will need to be ready, and a few small things are needed.
I've extracted a list of comments from the packaging policy, these may
impact the ant build.xml and/or README file contents:
- Programs and libraries should enable JUnit tests, if these are
present. The build may ignore test failures.
- Class files in a java library must be built with debug symbols.
- All jar files must have a well-documented CLASSPATH, so that
developers should know what to add to their wrappers.
- Java library packages should compile the javadoc API of the library.
The API must link against the javadoc API of the libraries it depends
on. This includes the core java classes, which are provided by
default-jdk-doc. The API must be registered with doc-base and must be
installed in /usr/share/doc/<package>/api/ or
- The API must be placed in a separate doc package. This package must
recommend the doc packages it was linked against.
- the Debian package has to be built from an official release of ice4j.
Therefore, you need to
a) tag a release (e.g. 1.0) in SVN
b) create a source distribution tarball (must not contain any compiled
.class files or copyright restricted items, RFCs are not permitted, for
example, but they can live in the repo)
c) put the tarball on a download page somewhere
Overall, I think this will be a good test run before packaging other
parts of Jitsi, because ice4j is standalone and doesn't have lots of
other dependencies itself.