In message: <[EMAIL PROTECTED]>
Ola Lundqvist <[EMAIL PROTECTED]> writes:
>On Sun, Oct 06, 2002 at 05:12:39PM +0200, Robert Bihlmeyer wrote:
>> As policy requires that all "binaries" (well, it's debatable whether
>> class files fall under this) should be built with debug info and
>> s
In message: <[EMAIL PROTECTED]>
Ola Lundqvist <[EMAIL PROTECTED]> writes:
>On Sun, Oct 06, 2002 at 05:12:39PM +0200, Robert Bihlmeyer wrote:
>> As policy requires that all "binaries" (well, it's debatable whether
>> class files fall under this) should be built with debug info and
>>
On Sun, Oct 06, 2002 at 05:12:39PM +0200, Robert Bihlmeyer wrote:
> As policy requires that all "binaries" (well, it's debatable whether
> class files fall under this) should be built with debug info and
> stripped when put into the package, I'd like to know whether there is
> a tool to strip debug
On Sun, Oct 06, 2002 at 05:12:39PM +0200, Robert Bihlmeyer wrote:
> As policy requires that all "binaries" (well, it's debatable whether
> class files fall under this) should be built with debug info and
> stripped when put into the package, I'd like to know whether there is
> a tool to strip debu
As policy requires that all "binaries" (well, it's debatable whether
class files fall under this) should be built with debug info and
stripped when put into the package, I'd like to know whether there is
a tool to strip debugging info from class files.
If not, maybe policy and/or java-policy shoul
As policy requires that all "binaries" (well, it's debatable whether
class files fall under this) should be built with debug info and
stripped when put into the package, I'd like to know whether there is
a tool to strip debugging info from class files.
If not, maybe policy and/or java-policy shou
6 matches
Mail list logo
