|
| Re: How to disable/replace eclipse logger implementation [message #325977 is a reply to message #325957] |
Tue, 04 March 2008 20:40   |
 Francis Upton IV
Messages: 472
Registered: July 2009
Location: Oakland, CA |
Senior Member |
|
|
umm, there is something wrong that is causing the logging to the log
file. I would figure out what that is first.
In my RCP app, I have a log handler that reports an error to the user
(and considers it a bug) whenever there is something logged. Therefore
my log file is virtually empty.
Roland Tepp wrote:
> Hello Everybody,
>
> I am trying to run an eclipse based application in an embedded
> environment with limited disk space and would like to severely limit
> eclipse log file (workspace/.metadata/.log) size.
>
> Currently it seems that the log file is grown until it reaches 1GB size,
> which is then renamed, backed up and new log file is created. This
> process is repeated until 10 backed up log files are created, thus
> increasing the total size of log files to 10GB, which is unacceptable.
>
> We would like to either entirely disable logging or replace default
> eclipse logger with our own, that we could control more tightly.
>
Platform UI Committer for Common Navigator
http://wiki.eclipse.org/index.php/Common_Navigator_Framework
http://help.eclipse.org/galileo/topic/org.eclipse.platform.d oc.isv/guide/cnf.htm
|
|
|
| Re: How to disable/replace eclipse logger implementation [message #326578 is a reply to message #325977] |
Tue, 25 March 2008 15:57 |
Roland Tepp
Messages: 336
Registered: July 2009 |
Senior Member |
|
|
Sorry Francis, but this did not answer my question.
I know that the eclipse logging facility is mostly used for logging
errors and warnings and most of these cases are "critical" enough to be
considered bugs in their own right.
But in addition to these items there are also info, debug and trace
level logs, that should also be logged at some point.
Current Eclipse practice of logging debug level logs to stdout is not
satisfying, since this separates conventional log messages from error
messages that could be relevant for debugging problems in the
testing/production environment.
What I need is to have the ability to redirect all logging statements to
a single location, irrespective of it's severity. I also do not want to
manage multiple logging facilities - one for reporting errors and
warnings and one for info/debug/trace level logging...
Also - the need to disable the eclipse log altogether is required in the
embedded environment without any writable disk space available.
Francis Upton kirjutas mulle midagi seesugust:
> umm, there is something wrong that is causing the logging to the log
> file. I would figure out what that is first.
>
> In my RCP app, I have a log handler that reports an error to the user
> (and considers it a bug) whenever there is something logged. Therefore
> my log file is virtually empty.
>
> Roland Tepp wrote:
>> Hello Everybody,
>>
>> I am trying to run an eclipse based application in an embedded
>> environment with limited disk space and would like to severely limit
>> eclipse log file (workspace/.metadata/.log) size.
>>
>> Currently it seems that the log file is grown until it reaches 1GB
>> size, which is then renamed, backed up and new log file is created.
>> This process is repeated until 10 backed up log files are created,
>> thus increasing the total size of log files to 10GB, which is
>> unacceptable.
>>
>> We would like to either entirely disable logging or replace default
>> eclipse logger with our own, that we could control more tightly.
>>
--
Roland Tepp
|
|
|
| Re: How to disable/replace eclipse logger implementation [message #326655 is a reply to message #326578] |
Thu, 27 March 2008 16:04 |
Uwe Stieber
Messages: 19
Registered: July 2009 |
Junior Member |
|
|
Hi,
have you considered to use java.util.logging? It would be easy to create log
handler which is fowarding Info/Error/Warning messages to the Eclipse error
log additional to capture the log record to where ever you want. From client
perspective, you always use the same interface and you do not need to care
about where the messages will end up. All the logic is centralized to the
log handler.
Regards, Uwe Stieber
"Roland Tepp" <roland@videobet.com> wrote in message
news:fsb7a0$e7f$1@build.eclipse.org...
> Sorry Francis, but this did not answer my question.
>
> I know that the eclipse logging facility is mostly used for logging errors
> and warnings and most of these cases are "critical" enough to be
> considered bugs in their own right.
>
> But in addition to these items there are also info, debug and trace level
> logs, that should also be logged at some point.
>
> Current Eclipse practice of logging debug level logs to stdout is not
> satisfying, since this separates conventional log messages from error
> messages that could be relevant for debugging problems in the
> testing/production environment.
>
> What I need is to have the ability to redirect all logging statements to a
> single location, irrespective of it's severity. I also do not want to
> manage multiple logging facilities - one for reporting errors and warnings
> and one for info/debug/trace level logging...
>
> Also - the need to disable the eclipse log altogether is required in the
> embedded environment without any writable disk space available.
>
> Francis Upton kirjutas mulle midagi seesugust:
>> umm, there is something wrong that is causing the logging to the log
>> file. I would figure out what that is first.
>>
>> In my RCP app, I have a log handler that reports an error to the user
>> (and considers it a bug) whenever there is something logged. Therefore
>> my log file is virtually empty.
>>
>> Roland Tepp wrote:
>>> Hello Everybody,
>>>
>>> I am trying to run an eclipse based application in an embedded
>>> environment with limited disk space and would like to severely limit
>>> eclipse log file (workspace/.metadata/.log) size.
>>>
>>> Currently it seems that the log file is grown until it reaches 1GB size,
>>> which is then renamed, backed up and new log file is created. This
>>> process is repeated until 10 backed up log files are created, thus
>>> increasing the total size of log files to 10GB, which is unacceptable.
>>>
>>> We would like to either entirely disable logging or replace default
>>> eclipse logger with our own, that we could control more tightly.
>>>
>
> --
> Roland Tepp
|
|
|
Powered by
FUDForum. Page generated in 0.03023 seconds
] 
Search
Help
Register
Login
Home
