Re: [jetty-dev] jetty debug options

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

well I don't think we have to standardize on that naming convention,
jetty.log.DEBUG is good with me as well and easily managed for system
properties...

the o.e.j.l.u.DEBUG is just awfully long for a system property...

jesse


--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Tue, Aug 11, 2009 at 19:16, Jan Bartel<janb@xxxxxxxxxxx> wrote:
> I think the distinction between -DDEBUG (or DEBUG=true) being for
> debug for start-up time logging vs org.eclipse.jetty.util.log.DEBUG
> being for "runtime" logging is an awfully subtle distinction, and
> one that is not at all obvious from the naming.
>
> Do we really have to have the distinction between the logging phases?
> Why can't org.eclipse.jetty.util.log.DEBUG work for both startup time
> and runtime? Granted that during startup its just going to be stderr
> output and during runtime its going to be via the StdErrLog, but there's no
> reason why those 2 mechanisms can't both check the same system property
> is there?
>
> And I have to admit that I'm not a huge fan of
> org.eclipse.jetty.util.log.DEBUG
> as a string either - any chance we could we have something a smidgin
> shorter, like "org.eclipse.jetty.DEBUG" or "org.eclipse.jetty.log.DEBUG"?
> Actually,
> in my heart-of-hearts I'd prefer just "jetty.log.DEBUG" ... but I guess
> we're standardizing on the "org.eclipse" prefix?
>
> Jan
>
>
>
> Joakim Erdfelt wrote:
>>
>> There's legacy, backwards compatibility, and elimination of System
>> properties all conspiring to make this confusing.
>>
>> Also, there's no more distinction between a JVM system property and a
>> start.jar property.
>>
>> These 2 command lines are equivalent now ...
>>
>> $ java -jar start.jar DEBUG=true
>> $ java -DDEBUG=true -jar start.jar
>>
>> (Note: you can have "DEBUG=true" in your start.ini as well)
>>
>> Then we have the distinction between the 2 keys ...
>>
>> DEBUG is for debugging the start.jar & classpath & configuration.
>> while org.eclipse.jetty.util.log.DEBUG is for turning on the DEBUG logging
>> severity level for the StdErrLog class.
>>
>> ---
>> Joakim Erdfelt / joakim@xxxxxxxxxxx <mailto:joakim@xxxxxxxxxxx>
>>
>>
>> On Tue, Aug 11, 2009 at 2:12 PM, Jesse McConnell
>> <jesse.mcconnell@xxxxxxxxx <mailto:jesse.mcconnell@xxxxxxxxx>> wrote:
>>
>>    I am not sure I am following the options for debug now...
>>
>>    -DDEBUG - I like this one :)
>>    -Dorg.eclipse.jetty.util.log.DEBUG - this one is a bit long in the
>>    typing..
>>
>>    but this?
>>
>>    java -jar start.jar DEBUG=true ?
>>
>>    can we narrow this down to...one, or maybe two?
>>
>>    I ask because I am having issues getting this sorted out with the
>>    --secure options in there as well and this was a bit of a
>>    distraction..
>>
>>    cheers,
>>    jesse
>>
>>    --
>>    jesse mcconnell
>>    jesse.mcconnell@xxxxxxxxx <mailto:jesse.mcconnell@xxxxxxxxx>
>>    _______________________________________________
>>    jetty-dev mailing list
>>    jetty-dev@xxxxxxxxxxx <mailto:jetty-dev@xxxxxxxxxxx>
>>    https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
> --
> Jan Bartel, Webtide LLC | janb@xxxxxxxxxxx | http://www.webtide.com
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>