Re: FUTEX_WAIT java - was iceweasel javaplugin

2009-12-16 Thread Alan Greenberger
On 2009-12-12, Alan Greenberger wrote: > Next I downloaded a trivial java test program from > http://freemind.sourceforge.net/wiki/index.php/FreeMind_on_Linux > javac DummyPrinter.java > strace java DummyPrinter > It hangs with: > futex(0xb7d6cbd8, FUTEX_WAIT, 1992, NULL > After three minutes

RFS: java-gnome 4.0.14-1

2009-12-16 Thread Onkar Shinde
Note: This version adds certain compiler flag in rules file to fix FTBFS on hppa. The sponsorer should check that it actually works. The latest changelog entry for reference: java-gnome (4.0.14-1) unstable; urgency=low * New upstream release. * debian/rules - Add compiler flag -ffunction-

Re: api docs, java source

2009-12-16 Thread Matthew Johnson
On Wed Dec 16 04:28, Pablo Duboue wrote: > apt-get source is neither convenient nor reasonable, particularly with > jars that are the result of complex builds involving ant, maven, etc. > If there are -dbg for other libraries why they can't be -dbg for java > ones? Besides the source code, having t

Re: api docs, java source

2009-12-16 Thread Vincent Fourmond
On Wed, Dec 16, 2009 at 10:28 AM, Pablo Duboue wrote: > On Wed, Dec 16, 2009 at 4:16 AM, Matthew Johnson wrote: >> On Wed Dec 16 03:58, Pablo Duboue wrote: >>> What about having -dbg versions of the jars that include the source code and >>> debug information? >> >> Java policy says (or will say)

Re: api docs, java source

2009-12-16 Thread Sylvestre Ledru
Le mercredi 16 décembre 2009 à 04:13 -0500, Pablo Duboue a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > > >> What about having -dbg versions of the jars that include the source code > >> and > >> debug information? > > What is "debug information" in the Java world ? > > Ac

Re: api docs, java source

2009-12-16 Thread Pablo Duboue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Dec 16, 2009 at 4:16 AM, Matthew Johnson wrote: > On Wed Dec 16 03:58, Pablo Duboue wrote: >> What about having -dbg versions of the jars that include the source code and >> debug information? > > Java policy says (or will say) that we sh

Re: api docs, java source

2009-12-16 Thread Sylvestre Ledru
Le mercredi 16 décembre 2009 à 03:58 -0500, Pablo Duboue a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > On Wed, Dec 16, 2009 at 3:51 AM, Marcus Better wrote: > > Onkar Shinde wrote: > >>> Would it be useful to have PACKAGE-dev packages for java containing the > >>> source co

Re: api docs, java source

2009-12-16 Thread Matthew Johnson
On Tue Dec 15 21:05, Onkar Shinde wrote: > Please file a bug. The docs should go to /usr/share/doc/junit4/api. > > > Maybe we should add a section to java-policy about the right position? I thought it was there, either currently or in the new draft. It certainly should be. The new version of java

Re: api docs, java source

2009-12-16 Thread Matthew Johnson
On Wed Dec 16 03:58, Pablo Duboue wrote: > What about having -dbg versions of the jars that include the source code and > debug information? Java policy says (or will say) that we should leave debugging symbols in the release version (don't compile with -g) anyway. As was said upthread, there's a

Re: api docs, java source

2009-12-16 Thread Pablo Duboue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> What about having -dbg versions of the jars that include the source code and >> debug information? > What is "debug information" in the Java world ? Actually, the .class files with debug info are so verbose that can be decompiled close to the o

Re: api docs, java source

2009-12-16 Thread Pablo Duboue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, Dec 16, 2009 at 3:51 AM, Marcus Better wrote: > Onkar Shinde wrote: >>> Would it be useful to have PACKAGE-dev packages for java containing the >>> source code, so that I can refer to it when developing on top of a >>> library? >> >> Ideall

Re: api docs, java source

2009-12-16 Thread Marcus Better
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Onkar Shinde wrote: >> Would it be useful to have PACKAGE-dev packages for java containing the >> source code, so that I can refer to it when developing on top of a >> library? > > Ideally you shouldn't refer to source code of libraries for writing >