I'd be unhappy to see yet more deprecated "APIs", i.e., would
org.eclipse.core.runtime.ILog be deprecated? Consumers might start to
feel as if no API is really API anymore. Everything is just potentially
in a transient state on the path to ultimate perfection, along with the
ever-present concern about deletion.
Of course I'm all for progress and improvements, so I'd not vote -1.
And I most certainly don't want to discourage progress or innovation.
My biggest concern is simply deprecation and deletion.
On 12.09.2019 18:13, Lars Vogel wrote:
+1
Dirk Fauth <dirk.fa...@googlemail.com
<mailto:dirk.fa...@googlemail.com>> schrieb am Do., 12. Sep. 2019, 18:07:
Actually I would like to get rid of the multiple facades
(FrameworkLog, RuntimeLog, etc. are all forwarding to the OSGi
LogService. And with OSGi R7 it has improved and probably makes
all the facades unnecessary. Why reinventing the wheel if the base
has fixed the issues from the past?
Lars Vogel <lars.vo...@vogella.com
<mailto:lars.vo...@vogella.com>> schrieb am Do., 12. Sep. 2019, 17:44:
I know that statement would trigger a reply. :-)
I think Dirk's vision is to deprecate all other logging
approaches or fascade them.
Would IMHO be nice to have one simple and fast way of logging.
For example, currently writing lots of entries to the error
log can cause UI freezes.
Mickael Istria <mist...@redhat.com
<mailto:mist...@redhat.com>> schrieb am Do., 12. Sep. 2019, 17:40:
On Thu, Sep 12, 2019 at 5:22 PM Lars Vogel
<lars.vo...@vogella.com <mailto:lars.vo...@vogella.com>>
wrote:
Having one logging solution would be great, as you
pointed out it must
be simple for the IDE case and the e4 RCP case.
As mentioned in the previous thread, there are already N
ways of logging, so adding one more way won't make N+1 == 1.
All the logging approach that are already in are most
likely meant to stay as API, so before starting such
refactoring, I think it needs to be verified how much
value is to be expected from it.
As spotted in the "only few committers care of know the
details about logging", I think that most contributors
don't really care about logging because while it might be
not perfect, it just works fine in the current state and
changing this wouldn't provide much added value to them.
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password,
or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org <mailto:platform-dev@eclipse.org>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
