Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 265445 - Message "Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed." logged multiple times
Summary: Message "Authorization infrastructure (org.eclipse.core.runtime.compatibility...
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Runtime (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 3.5 M6   Edit
Assignee: platform-runtime-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-19 07:39 EST by Gunnar Wagenknecht CLA
Modified: 2009-02-19 10:23 EST (History)
0 users

See Also:

Attachments
Patch for org.eclipse.core.runtime to log the message only once (1.20 KB, patch)
2009-02-19 07:39 EST, Gunnar Wagenknecht CLA 		john.arthorne: iplog+
Details | Diff
Patch for org.eclipse.core.runtime to print the message only when debug is on (1.09 KB, patch)
2009-02-19 07:45 EST, Gunnar Wagenknecht CLA 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2009-02-19 07:39:57 EST 
Created attachment 126155 [details]
Patch for org.eclipse.core.runtime to log the message only once

When org.eclipse.core.runtime is deployed without org.eclipse.core.runtime.compatibility.auth the message "Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed." is logged multiple times in the log file.

The attached patch adds a boolean flag to log the message only once.
Comment 1 Gunnar Wagenknecht CLA 2009-02-19 07:45:20 EST 
Created attachment 126156 [details]
Patch for org.eclipse.core.runtime to print the message only when debug is on

I wonder if this message needs to be logged at all. This patch takes a different approach. It turns the message into a debug message which will be printed only when debug is enabled.
Comment 2 John Arthorne CLA 2009-02-19 08:50:53 EST 
Note that each time this is logged, it means someone called platform authorization APIs. If you are seeing this logged many times, it suggests you have something installed that requires the authorization API. You should really either stop using the APIs (or stop using the functionality that uses the APIs), or add back the authorization fragment. We could consider logging only once per session, but I'm a bit worried this means things will be failing and there won't be any indication of the failure in the log.
Comment 3 Gunnar Wagenknecht CLA 2009-02-19 09:26:58 EST 
I'm not using the authentication component. That's why I left it out in my deployment. This means that something else is calling it. However, I use only Equinox and a set of other org.eclipse.core plug-ins. Maybe some debug output with a full stack trace would be a better idea?
Comment 4 Gunnar Wagenknecht CLA 2009-02-19 09:34:42 EST 
Ok, so it's org.eclipse.mylyn.tasks.core. There is already a TODO tag in their code to move to the new API so I don't need to open a bug for it. But since I'm not affected by this piece of functionality I really wonder if there is a way to turn off that logging.  The issue is that this is really flooding the log files which doesn't make sense on a server. 

But as a workaround, I seems easier to just deploy the authentication component for now.
Comment 5 John Arthorne CLA 2009-02-19 10:22:52 EST 
I have released the first patch (after fixing compile error due to modifying a final field).