More on the execution failure on Debian

2 views
Skip to first unread message

Sebastian Humenda

unread,
Jul 31, 2013, 10:36:28 AM7/31/13
to braill...@googlegroups.com
Hi,

I would like to give more information so that we can quickly resolve my
packaging failure related to the class path.

I changed the hard-coded path's to the lib/*.jar-files in order to build
correctly on Debian. I attached the modified build.xml. Could you please have a
look?
I changed the path's from line 87 on and the *.jar-inclusion in line 360.
The latter was needed to not include the lib/-directory, at least I thought so.

Thanks!
Sebastian
--
Web: http://www.crustulus.de | Blog (eng / deu): http://www.crustulus.de/blog
Freies Latein-Deutsch-Wörterbuch: http://www.crustulus.de/freedict.de.html
FreeDict: Free multilingual dictionary databases - http://www.freedict.org
signature.asc

Joel Håkansson

unread,
Aug 20, 2013, 8:22:58 AM8/20/13
to braill...@googlegroups.com
Hi Sebastian,

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)!

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. :)

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.

Or I could update the build.debian.properties for you. Let me know.

Best,
Joel


-----Ursprungligt meddelande-----
Från: braill...@googlegroups.com [mailto:braill...@googlegroups.com] För Sebastian Humenda
Skickat: den 31 juli 2013 16:36
Till: braill...@googlegroups.com
Ämne: More on the execution failure on Debian

Sebastian Humenda

unread,
Aug 21, 2013, 12:27:28 PM8/21/13
to braill...@googlegroups.com
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 :).
signature.asc

Sebastian Humenda

unread,
Aug 21, 2013, 12:28:53 PM8/21/13
to braill...@googlegroups.com
Hi again,

I forgot to ask: where have you done your changes, in trunk/ or in the actual
release (https://brailleutils.googlecode.com/svn/)?

Thanks
signature.asc
Reply all
Reply to author
Forward
0 new messages