0006261: Properly manage log in rebuild process

Description

Rebuild process is not showing all the log that appears when the same ant commands are executed in command line.

The problem is that some of this log goes to the standard output instead to the log4j logger. This was fixed redirecting the standard output to be shown in the console but this caused issue 0006248 so it was reverted, another problem of this approach is that redirecting the output it is not only displayed the log for the current process but all the log that was supposed to be showed in the standard output.

Ideally this management should be done using log4j and not standard output.

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to	defect	0006248	closed	alostale	Error 500 building a module
related to	defect	0006088	closed	mtaal	Modularity: compilation errors are not in the log
depends on	defect	0005926	closed	mtaal	Rebuilds are not logged in Installation History

Notes
(0011927) mtaal (manager) 2009-01-06 11:19	Was resolved together with the issues it relates to. A separate log4j logger is defined in log4j.lcf, this logger is used to log messages from the build.

Issue History
Date Modified	Username	Field	Change
2008-11-28 17:32	alostale	New Issue
2008-11-28 17:32	alostale	Assigned To	=> marvintm
2008-11-28 17:32	alostale	sf_bug_id	0 => 2356198
2008-11-28 17:32	alostale	Regression testing	=> No
2008-11-28 17:32	alostale	Relationship added	related to 0006248
2008-11-28 17:33	alostale	Relationship added	related to 0006088
2008-12-15 10:16	rafaroda	Status	new => scheduled
2008-12-15 10:16	rafaroda	fix_in_branch	=> trunk
2009-01-05 18:45	iciordia	Assigned To	marvintm => mtaal
2009-01-06 11:17	mtaal	Relationship added	depends on 0005926
2009-01-06 11:19	mtaal	Note Added: 0011927
2009-01-06 11:19	mtaal	Status	scheduled => resolved
2009-01-06 11:19	mtaal	svn_revision	=> 11471
2009-01-06 11:19	mtaal	fix_in_branch	trunk =>
2009-03-06 12:52	psarobe	Status	resolved => closed