You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by James Carman <ja...@carmanconsulting.com> on 2008/03/19 14:37:40 UTC
[DISCUSS] Distribution jars and debug compiler setting...
All,
We were discussing in another thread about the merits of the
dependencies report from m2 when I noticed our report that tells us if
the dependency was compiled with debug turned on or not (this should
be part of the default m2 report if it isn't already). Anyway, I was
thinking that maybe our distributions should be compiled with debug
turned off by default and we should also have a version that has it
turned on for folks to download if they need it. Either way, we
should probably offer two different versions. I don't really care
what the default is. We could use maven classifiers to distinguish
between the two. Thoughts?
James
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Distribution jars and debug compiler setting...
Posted by Henri Yandell <fl...@gmail.com>.
Debug on, and people who want it off can build it themselves with
instructions we provide [so we need said instructions] :)
Hen
On Wed, Mar 19, 2008 at 6:37 AM, James Carman
<ja...@carmanconsulting.com> wrote:
> All,
>
> We were discussing in another thread about the merits of the
> dependencies report from m2 when I noticed our report that tells us if
> the dependency was compiled with debug turned on or not (this should
> be part of the default m2 report if it isn't already). Anyway, I was
> thinking that maybe our distributions should be compiled with debug
> turned off by default and we should also have a version that has it
> turned on for folks to download if they need it. Either way, we
> should probably offer two different versions. I don't really care
> what the default is. We could use maven classifiers to distinguish
> between the two. Thoughts?
>
> James
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [DISCUSS] Distribution jars and debug compiler setting...
Posted by Gary Gregory <GG...@seagullsoftware.com>.
> -----Original Message-----
> From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
> On Behalf Of James Carman
> Sent: Wednesday, March 19, 2008 12:41 PM
> To: Jakarta Commons Developers List
> Subject: Re: [DISCUSS] Distribution jars and debug compiler setting...
>
> On 3/19/08, Gary Gregory <GG...@seagullsoftware.com> wrote:
> >
> > What the argument for debug off? Saving disc space?
>
> Performance.
Really? I thought debug just added a source line number to PC table at the end of the class file?
Gary
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [DISCUSS] Distribution jars and debug compiler setting...
Posted by James Carman <ja...@carmanconsulting.com>.
On 3/19/08, Gary Gregory <GG...@seagullsoftware.com> wrote:
>
> What the argument for debug off? Saving disc space?
Performance.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
RE: [DISCUSS] Distribution jars and debug compiler setting...
Posted by Gary Gregory <GG...@seagullsoftware.com>.
I like debug on.
When a customer has an issue that needed debugging level information it is tricky enough that we have to guide them on how to turn on debugging and other particulars for our software and then try again. Now, I'd have to either change our build to include debug jars instead of plain jars, bleh. And I would hope that the debug jars not be called *-debug, because I'd want to rename those to the normal name. And what about manifests? A commons component that depends on other commons jar would need to depend on the right debug or non-debug versions. More room for errors, more headaches.
What the argument for debug off? Saving disc space?
Thank you,
Gary
> -----Original Message-----
> From: jcarman@carmanconsulting.com [mailto:jcarman@carmanconsulting.com]
> On Behalf Of James Carman
> Sent: Wednesday, March 19, 2008 6:38 AM
> To: Jakarta Commons Developers List
> Subject: [DISCUSS] Distribution jars and debug compiler setting...
>
> All,
>
> We were discussing in another thread about the merits of the
> dependencies report from m2 when I noticed our report that tells us if
> the dependency was compiled with debug turned on or not (this should
> be part of the default m2 report if it isn't already). Anyway, I was
> thinking that maybe our distributions should be compiled with debug
> turned off by default and we should also have a version that has it
> turned on for folks to download if they need it. Either way, we
> should probably offer two different versions. I don't really care
> what the default is. We could use maven classifiers to distinguish
> between the two. Thoughts?
>
> James
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org