[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse.org-architecture-council] Bug 358968 - policy for configuring logging systems such as commons logging
|
What ‚kind' of work do you have in mind? The class Logger doesn’t look like it got much love in the past and it’s API doesn’t offer much.
My current feeling is to get rid of that API and recommend Eclipse plugin developers to use one of the already existing logging APIs - like SLF4J. However, it’s unclear to me whether recommending to use some non-eclipse Logging API is something the architecture council would like to do. Any comments on this?
Marcel
Am 18.07.2014 um 16:01 schrieb Tom Schindl <tom.schindl@xxxxxxxxxxxxxxx>:
> Hi,
>
> There's one more logging API which is part of
> org.eclipse.e4.core.services.log - IMHO this API is a complete mess and
> needs to be completely revised but is marked as provisional maybe you
> could do your work in this bundle?
>
> Tom
>
> On 18.07.14 13:59, Marcel Bruch wrote:
>> Hi architecture council,
>>
>> Bug 358968 - policy for configuring logging systems such as commons logging [1] has been discussed many times. Some time ago, I proposed to use SLF4J bridging APIs as solution to this problem. Now, I’d like to share a set of slides [2] that summarize the current state of the proposed solution and get your feedback on it. Please note that the ultimate goal would be to add this feature/code into the Eclipse Rcp platform for Mars. Thus, please share your thoughts and let me know about any blocker issues you may see. Supporting +1’s are appreciated as well.
>>
>>
>> Looking forward to your comments.
>>
>> Best,
>> Marcel
>>
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=358968
>> [2] https://drive.google.com/file/d/0B9Gf8BD0WA1SV1NFUFluTmpFOHM/edit?usp=sharing
>> _______________________________________________
>> eclipse.org-architecture-council mailing list
>> eclipse.org-architecture-council@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
>>
>> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
>>
>
> _______________________________________________
> eclipse.org-architecture-council mailing list
> eclipse.org-architecture-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-architecture-council
>
> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
