Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Platform » Customized .log file location
Customized .log file location [message #496996] Thu, 12 November 2009 07:41 Go to next message
Daniel Krügler is currently offline Daniel KrüglerFriend
Messages: 853
Registered: July 2009
Senior Member
It is an user-request of high priority for our RCP programs that
the log files (primarily the .log file, but there are two different
log files types as well from the Eclipse framework) should be positioned
at a different location than the default location (workspace/.metadata).

The important point is: The decision for this needs to support a
*dynamic* and programmatic specification and cannot be provided as
constants in the launching configuration.

I would be very happy if someone could give me a pointer how this may be
realized. During a class search related to logging I stumbled across
FrameworkAdaptor, AdaptorHook, and BaseAdaptor, but it is unclear to me:

a) Which of these needs to be implemented (if at all) and how that can
be done in a way that restricts to the specification of the log file
location (E.g. I don't want to re-implement BaseAdaptor, if possible)

b) How to "inject" this implementation into the RCP such that it will be
used (I use a feature based headless build, if this information is
relevant).

Thanks in advance,

Daniel Krügler
Re: Customized .log file location [message #500129 is a reply to message #496996] Wed, 25 November 2009 07:02 Go to previous messageGo to next message
Daniel Krügler is currently offline Daniel KrüglerFriend
Messages: 853
Registered: July 2009
Senior Member
Daniel Krügler wrote:
> It is an user-request of high priority for our RCP programs that
> the log files (primarily the .log file, but there are two different
> log files types as well from the Eclipse framework) should be positioned
> at a different location than the default location (workspace/.metadata).
>
> The important point is: The decision for this needs to support a
> *dynamic* and programmatic specification and cannot be provided as
> constants in the launching configuration.
>
> I would be very happy if someone could give me a pointer how this may be
> realized. During a class search related to logging I stumbled across
> FrameworkAdaptor, AdaptorHook, and BaseAdaptor, but it is unclear to me:
>
> a) Which of these needs to be implemented (if at all) and how that can
> be done in a way that restricts to the specification of the log file
> location (E.g. I don't want to re-implement BaseAdaptor, if possible)
>
> b) How to "inject" this implementation into the RCP such that it will be
> used (I use a feature based headless build, if this information is
> relevant).

I'm a bit surprised that no-one else seems to think that this is an
important feature. I have been asking this question over several
years and I got never a reply. So the only way to fix this seems
to be that the installation modifies the configuration file.
Personally I'm not happy with that solution but at least it is
a work-around.

- Daniel
Re: Customized .log file location [message #505525 is a reply to message #496996] Thu, 31 December 2009 17:52 Go to previous message
Benjamin Leipold is currently offline Benjamin LeipoldFriend
Messages: 13
Registered: July 2009
Junior Member
If .log log file may still exists and early log events can be ignored, you can register your own log listener via Platform.addLogListener(ILogListener). Than your are free to do anything you want with log events.
Previous Topic:Centralized Exception handling for Eclipse plug-in
Next Topic:Problem: unicode quotation marks in gcc4 compiler messages
Goto Forum:
  


Current Time: Tue Mar 19 08:01:32 GMT 2024

Powered by FUDForum. Page generated in 0.02380 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top