Bug 268120 - All log output directed to System.out when running headless
Summary: All log output directed to System.out when running headless
Status: RESOLVED FIXED
Alias: None
Product: AJDT
Classification: Tools
Component: Core (show other bugs)
Version: 1.6.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.0.0   Edit
Assignee: AJDT-inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-11 10:27 EDT by Vladimir Piskarev CLA
Modified: 2009-05-11 17:49 EDT (History)
1 user (show)

See Also:

Attachments
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 Vladimir Piskarev CLA 2009-03-11 10:27:42 EDT 
When running headless (i.e. without o.e.ajdt.ui) there is no IAJLogger and all AJDT output is printed to System.out. This is very verbose.
Comment 1 Andrew Eisenberg CLA 2009-03-12 18:43:48 EDT 
Would be nice to specify a custom logger, or to specify a null logger.  Perhaps this can be done through an environment variable.

Do you have any specific suggestions?

As you are finding out, AJDT was not designed to be run headless.  However, this is something that we can work on in future releases of AJDT.
Comment 2 Vladimir Piskarev CLA 2009-03-13 03:02:48 EDT 
Well, ideally it would be something using Eclipse tracing.
Comment 3 Andrew Eisenberg CLA 2009-04-03 18:24:12 EDT 
Instead of logging to stdout if there is no logger installed, the following is done:

	AspectJPlugin.getDefault().getLog().log(new Status(IStatus.INFO, AspectJPlugin.PLUGIN_ID, msg));
	
As before, it is also possible to install your own logger that logs to dev/null.