Bug 96605

Summary:	JDTCompilerAdapter should allow a log without all verbose information
Product:	[Eclipse Project] JDT	Reporter:	Pascal Rapicault <pascal>
Component:	Core	Assignee:	Olivier Thomann <Olivier_Thomann>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	gunnar
Version:	3.1
Target Milestone:	3.1 RC2
Hardware:	PC
OS:	Windows 2000
Whiteboard:
Bug Depends on:
Bug Blocks:	96266, 96434

Description Pascal Rapicault

2005-05-25 09:36:44 EDT

Yesterday Olivier and I had a brief chat about the possibility to turnoff the
verbose mode and set -log when running the eclipse build. We quickly tested that
the .log files were being created, however we were not using the adapter, but
directly the main class, which seems to have a slightly different behavior.
Long story short, when I set verbose to false and set -log in the compilerarg I
don't get any log file which is annoying.

Comment 1 Olivier Thomann

2005-05-25 09:56:34 EDT

If -log doesn't specify a log file name, we should create a default one in the
destination directory.

Comment 2 Gunnar Wagenknecht

2005-05-25 10:35:18 EDT

I agree that this would be more clear than the javacVerbose=true magic.

Comment 3 Olivier Thomann

2005-05-25 12:45:21 EDT

In fact, this is more a feature request. Right now, -log requires a file name to
be specified.
I will investigate how we can add the creation of a default log file when no
name is specified.

Comment 4 Olivier Thomann

2005-05-26 10:21:04 EDT

Change title to reflect the right issue.
What we want to speed up the build process is a way to get the log without all
the verbose information. Right now the verbose mode is used to retrieve the log.
The nested compilerarg cannot be used to be compatible with javac.

Comment 5 Olivier Thomann

2005-05-27 15:07:59 EDT

I suggest commenting out the line that sets up the -verbose mode of the batch
compiler inside the ant adapter. This would minimize the changes. Keeping
verbose on in the ant task would generate a log as it is done now without
getting all the tracing in System.out.
The batch compiler could still be used as it is today.
If a user really wants the verbose mode, this could always be done using a
compilerarg.

Comment 6 Olivier Thomann

2005-05-30 09:25:14 EDT

Fixed by not activating the verbose option of the batch compiler when the
verbose mode of the ant task is enabled.
This should reduce the noise in the System.out. If users want the previous
behavior back, they can always add a nested compiler argument element that
contains "-verbose".

Comment 7 Olivier Thomann

2005-06-07 14:20:54 EDT

Verified in N20050606-0010 + JDT/Core HEAD

Comment 8 David Audel

2005-06-10 07:52:47 EDT

Verified for 3.1 RC2 using build I20050610-0010