Hallo Joel,
Joel Håkansson schrieb am 20.08.2013, 14:22 +0200:
>I finally had a look into your suggested changes, and given that you specify
>
>ant -DuseExternalJarsOnLinux=true
>
>things should already work out as you wished (almost). It seems that Bert had
>already done an excellent job on this (no surprise there)!
That really sounds great! Thanks for investigating this!
>The only thing that was missing was the removal of the external dependencies
>from the zip-file. I have added that to the build-script now. It does strike me
>as a bad idea to have a build that you cannot actually run without moving the
>files to another location (all jars in the same folder), but I'll let that go
>for now. :)
I have no idea how other Java packagers solve this, but *I* think you should use
absolute paths. Every package has a symlink in /usr/share/java, BUT the jar file
could be at /usr/share/maven-repo/some_dubious_path/package/package.jar as well
and if someone this as the class path entry, the rest of the dependencies cannot
be found.
>If you still need to update the Saxon path from saxonb.jar to saxon.jar you
>could add -Dfile.reference.saxon=/usr/share/java/saxon.jar to the build
>command.
Hm, which one was / is the right, saxonb or saxon?
>Or I could update the build.debian.properties for you. Let me know.
This one I would patch myself, thanks :).