-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Great, I misunderstood the earlier comment about -g, so glad we're not
shipping with -g:none.
Niels, for your draft, do you want to include some comments about
"apt-get source" for people interested in getting the source for
debugging purposes? I'
On Sat Dec 19 15:57, Niels Thykier wrote:
> > See above, policy (I thought?) says that we don't provide stripped
> > libraries, since in Java it doesn't give much of a performance
> > improvement, but it's very useful for things like debugging and (iirc?)
> > eclipse completion.
>
> I could not fi
Hi
Matthew Johnson wrote:
> On Wed Dec 16 04:28, Pablo Duboue wrote:
>> [...]
>> The objective of packing java libraries is so people don't need to
>> fetch and compile them themselves. If we only provide stripped
>> libraries with no source they will be good for execution but not for
>> developme
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
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)
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
-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
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
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
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
-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
-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
-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
>
On Tue, Dec 15, 2009 at 8:41 PM, Thomas Koch wrote:
> Hi,
>
> I just noticed, that junit4-doc installs api docs into /usr/share/java/junit4
> while ant-doc installs them into /usr/share/doc/ant/api.
Please file a bug. The docs should go to /usr/share/doc/junit4/api.
> Maybe we should add a secti
Hi,
I just noticed, that junit4-doc installs api docs into /usr/share/java/junit4
while ant-doc installs them into /usr/share/doc/ant/api.
Maybe we should add a section to java-policy about the right position?
questions:
a)
Where to put api docs?
- /usr/share/java/PACKAGE
- /usr/share/doc/PAC
15 matches
Mail list logo
