Hi Java developers,
One problem that I haven't solved so far is how to get the classpath
into the MANIFEST file as was proposed earlier in this thread.
As you may have remarked from my earlier posts I am working with the
JPackage guys recently. Their "recommendation to Java developers"
arguments against adding classpaths to the manifest. Probably the first
three arguments do not apply to the Debian environment, but the last one
may. I have not yet made up my mind on that. I just didn't want you to
loose their arguments:
"Do not use Class-Path references in MANIFESTs
The Class-Path system of MANIFESTs is evil because:
* It doesn't work with JDK 1.x.
* It only works at runtime, not at build time.
* It only works for a specific installation hierarchy.
* It can not be configured.
Wrapper scripts are much versatile and universal. We provide a set of
convenient shell helper functions for setting up such Unix scripts
easily (see jpackage-utils in project CVS)." [1]
You may also have a look at their build support system as they have some
quite useful helper scripts as well. jpackage-utils is available in
universe/contrib.
And as Richard was asking earlier how to identify dependencies within
jar packages: I am using Matthew's java-propose-classpath a lot and it
works fine (Thank you Matthew!). But sometimes it seems to miss some
dependencies, I have not yet found out why. Maybe it's just a
configuration error on my side. I also found
http://www.kirkk.com/main/Main/JarAnalyzer. Looks promising as it should
give you all dependencies in one run. Has anybody of you already used this?
Cheers,
Florian
[1] http://www.jpackage.org/jpprequest.php
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
