RE: [jdt-dev] Option for verbose JDT output/logging

["Scott Delap" <scott@xxxxxxxxxxxxxx>]

Often 3 hours will be with no errors.  I would guess we have a very detailed
project dependency tree.  I just started at the company but there are about
300 projects in the workspace with varying relationships.  I've had to do
clean for a number of reasons.  Often it is after I change a compiler
warning or when Eclipse locks up and seems to require a clean to get out of
a corrupt state when I restart it.  I try not to do a clean =).  The build
time seems to be all over the place.  Originally I thought it might be
related to AJDT and AspectJ.  I'm still working with the AJDT guys to see if
the problem is there.  However, I thought I'd go down the JDT route as well.
Earlier this week I could run clean/build repeatedly and it would always
take about 20 minutes.  Today I turned on the compiler warning for unused
else blocks and it has been running for hours.  Shouldn't clean/build run
the same process everytime?  I could understand if different incremental
builds take differing amounts of time.  However, shouldn't clean just remove
everything and start fresh?

Scott

-----Original Message-----
From: jdt-dev-admin@xxxxxxxxxxx [mailto:jdt-dev-admin@xxxxxxxxxxx] On Behalf
Of Kent Johnson
Sent: Thursday, December 02, 2004 3:01 PM
To: jdt-dev@xxxxxxxxxxx
Subject: Re: [jdt-dev] Option for verbose JDT output/logging

I suggest you open a bugzilla PR with more detail so we can track this down.


How many errors do you have in your projects?

Are any projects failing to build?

Do you have cycles in your project dependencies?

Is the 3 hour build repeatable once it happens or does the next build take 
20 minutes?


BTW: Why are you doing 'clean builds'? Is the incremental build not 
working for you?




"Scott Delap" <scott@xxxxxxxxxxxxxx> 
Sent by: jdt-dev-admin@xxxxxxxxxxx
12/02/2004 03:04 PM
Please respond to
jdt-dev


To
<jdt-dev@xxxxxxxxxxx>
cc

Subject
[jdt-dev] Option for verbose JDT output/logging






I have about 500megs of source in my project.  Sometimes a clean/build 
takes 20 minutes other times it takes 3 hours.  I would think the process 
of clean then build would be the same each time and reasonable consistent 
time wise.  Is there any way to turn on a verbose mode so I can attempt to 
see where the slowdowns are. Often I simply get an "Operation in progress" 
dialog with no option for details.  I'm then forced to just wait.
 
Scott

_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/jdt-dev