Logback and Java requirement

[Thorbjørn Ravn Andersen-2]

Hi Ceki.

I just migrated an elderly application using log4j and jcl to logback
except logback doesn't run under Java 1.4 (which is what I have on this
AS/400).  Bummer.  I wanted the markers to be able to filter on
threads.  Oh well.

I could not locate anywhere on the logback pages that Java 5 is a hard
requirement (but it was mentioned way down in a slf4j page).  I'd
suggest you add a notice to the download page.

(And it appears that http://retrotranslator.sourceforge.net/ works with
logback under 1.4, but that
stack traces look somewhat strange, I'll look into that later)

--
  Thorbjørn Ravn Andersen  "...plus... Tubular Bells!"

_______________________________________________
logback-dev mailing list
logback-dev@...
http://qos.ch/mailman/listinfo/logback-dev

[Ceki Gulcu-2]

Thorbjørn Ravn Andersen wrote:
> Hi Ceki.
>
> I just migrated an elderly application using log4j and jcl to logback
> except logback doesn't run under Java 1.4 (which is what I have on this
> AS/400).  Bummer.  I wanted the markers to be able to filter on
> threads.  Oh well.

Sorry to hear about the wasted effort. Did you use the slf4j-migrator?

> I could not locate anywhere on the logback pages that Java 5 is a hard
> requirement (but it was mentioned way down in a slf4j page).  I'd
> suggest you add a notice to the download page.

It's documented: http://logback.qos.ch/dependencies.html

> (And it appears that http://retrotranslator.sourceforge.net/ works with
> logback under 1.4, but that
> stack traces look somewhat strange, I'll look into that later)

Earlier versions of logback offered retrotranslated jar. However, we did not
want to bother with testing and maintaining that. (It is a thankless job).

If you wish, you can add it back by reversing the changes at:

http://svn.qos.ch/viewvc?view=rev&revision=1660

The last time I checked the retrotranslated code worked pretty well. However,
that was over 6 months ago.

HTH,

--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
logback-dev mailing list
logback-dev@...
http://qos.ch/mailman/listinfo/logback-dev

[Thorbjørn Ravn Andersen-2]

Ceki Gulcu skrev:
>
>> I just migrated an elderly application using log4j and jcl to logback
>> except logback doesn't run under Java 1.4 (which is what I have on this
>> AS/400).  Bummer.  I wanted the markers to be able to filter on
>> threads.  Oh well.
>>    
>
> Sorry to hear about the wasted effort. Did you use the slf4j-migrator?
>  

Didn't notice if I did.  I just downloaded the slf4j distribution and
dropped in the bridge jars plus the API, and played shortly with the
jdk14 jar but decided to go for retroweaver (didn't work well enough)
which again led to retrotranslator.

It runs now so the effort wasn't wasted, but I have requested that Java
5 gets installed so I can use the original versions of the jars (that
kind of hoop jumping makes me a little worried).  That will probably
take quite some time, so I'll use this to get on with the actual problem.

>> I could not locate anywhere on the logback pages that Java 5 is a hard
>> requirement (but it was mentioned way down in a slf4j page).  I'd
>> suggest you add a notice to the download page.
>>    
>
> It's documented: http://logback.qos.ch/dependencies.html
>  
Right you are.  Shame on me for not reading all the documentation before
downloading.  I believe that it was just the "logback is log4j reborn so
it probably would say if the JDK requirement was different" unconscious
thought that tricked me there.  Oh well.

>> (And it appears that http://retrotranslator.sourceforge.net/ works with
>> logback under 1.4, but that
>> stack traces look somewhat strange, I'll look into that later)
>>    
>
> Earlier versions of logback offered retrotranslated jar. However, we did not
> want to bother with testing and maintaining that. (It is a thankless job).
>  
I believe that!  

And all that just because that Sun decided that JDK 5.0 unconditionally
should compile to a new byte code format.  Sigh sigh sigh.


> If you wish, you can add it back by reversing the changes at:
>
> http://svn.qos.ch/viewvc?view=rev&revision=1660
>
> The last time I checked the retrotranslated code worked pretty well. However,
> that was over 6 months ago.
>  
Thank you for pointing it out, but no I don't want to go that way if I
can possibly help it.

I'll cross my fingers and hope that the powers that be find the time to
put Java 5 on these boxes.

(Time passes differently in our world, as you might have guessed :)

--
  Thorbjørn Ravn Andersen  "...plus... Tubular Bells!"

_______________________________________________
logback-dev mailing list
logback-dev@...
http://qos.ch/mailman/listinfo/logback-dev

[Ceki Gulcu-2]

Thorbjørn Ravn Andersen wrote:
> Ceki Gulcu skrev:
>> Sorry to hear about the wasted effort. Did you use the slf4j-migrator?
>>  
>
> Didn't notice if I did.  


slf4j-migrator is a visual application [1]. You have to launch it and
make choices by clicking on radio-buttons and such. If you had used it
you would remember, unless of course, it was such a painful experience
and you had to get your memory erased, as in "Eternal Sunshine of the
Spotless Mind" [2].

[1] http://www.slf4j.org/migrator.html
[2] http://www.imdb.com/title/tt0338013/

--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
_______________________________________________
logback-dev mailing list
logback-dev@...
http://qos.ch/mailman/listinfo/logback-dev

[Thorbjørn Ravn Andersen-2]

Ceki Gulcu skrev:

> Thorbjørn Ravn Andersen wrote:
>  
>> Ceki Gulcu skrev:
>>    
>>> Sorry to hear about the wasted effort. Did you use the slf4j-migrator?
>>>  
>>>      
>> Didn't notice if I did.  
>>    
>
>
> slf4j-migrator is a visual application [1]. You have to launch it and
> make choices by clicking on radio-buttons and such. If you had used it
> you would remember, unless of course, it was such a painful experience
> and you had to get your memory erased, as in "Eternal Sunshine of the
> Spotless Mind" [2].
>  

In that case I can say for certain I didn't.  The bridge jars was to
keep the log statements unmodified, and as such worked well.

When it comes to migrate the statements I'll use refactoring in Eclipse,
since I am familiar with it and knows it can do the task, so sorry, no :)

--
  Thorbjørn Ravn Andersen  "...plus... Tubular Bells!"

_______________________________________________
logback-dev mailing list
logback-dev@...
http://qos.ch/mailman/listinfo/logback-dev