Re: [aspectj-users] After clean build, eclipse continues to use the proc

[Konstantinos Kougios <ariskk@xxxxxxxxxxxx>]

Indeed there was no output message from AJDT after the build was 
finished. Eclipse though keeps my machine busy for a while after the 
build. Progress view displays "No operations to display at this time.". 
Maybe it's some other plugin, i.e. the subeclipse or the spring IDE.

This is the output from the AspectJ Event trace view:

22:26:6 Startup information:
  AJDT version: 1.5.0.200701291123 for Eclipse 3.2
  AspectJ Compiler version: DEVELOPMENT
  usingVisualiser=true
  usingXref=true
  usingCUprovider=false
  doneAutoOpenXRefViewD:/Work/Java = true
  org.aspectj.ajdt.core.compiler.weaver.XNoInline = true
  ajde.version.at.previous.startup = @AJDEVERSION@
  org.aspectj.ajdt.core.compiler.lint.BrokeSerialVersionCompatibility = 
warning
  promptForAutoOpenCrossReference = false
  org.aspectj.ajdt.core.compiler.lint.NeedSerialVersionUIDField = error
22:27:25 Removed problems and tasks for project iWilliam
22:27:32 Builder: Tidied output folder(s), deleted 1737 .class files
22:27:32 Removed problems and tasks for project mobile.phone.shop
22:27:32 Builder: Tidied output folder(s), deleted 50 .class files
22:27:32 Removed problems and tasks for project pathfinder
22:27:33 Builder: Tidied output folder(s), deleted 110 .class files
22:28:20 
===========================================================================================
22:28:20 Build kind = FULLBUILD
22:28:20 Project=iWilliam, kind of build requested=Full AspectJ compilation
22:28:20 Builder: Tidied output folder(s), deleted 0 .class files
22:28:28 Preparing for build: not going to be incremental because no 
successful previous full build
22:28:46 Timer event: 25764ms: Time to first compiled message
22:28:46 Timer event: 25921ms: Time to first woven message
22:29:12 AspectJ reports build successful, build was: FULL
22:29:13 AJDE Callback: finish. Was full build: true
22:29:13 Timer event: 52700ms: Total time spent in AJDE
22:30:0 Timer event: 766ms: Create element map (378 rels in project: 
iWilliam)
22:30:0 Types affected during build = 1669
22:30:30 Timer event: 31ms: Add markers (146 markers)
22:30:30 Timer event: 130445ms: Total time spent in AJBuilder.build()

Matt Chapman wrote:
> Try opening the AJDT Event Trace View (Window > Show View > Other > 
> AspectJ)
> During a build you'll then see messages to indicate the completion of
> various phases, such as the actual compilation and then generation of
> the crosscutting relationship map. After that AJDT shouldn't be doing
> anything else to tie up the CPU. You could also try opening the
> Progress view to see if anything else is shown there.
>
> Regards,
>
> Matt.
>
> On 30/01/07, Konstantinos Kougios <ariskk@xxxxxxxxxxxx> wrote:
> > Hi,
> >
> >
> >
> >             I work for a fairly large project. After doing a clean build
> > and the build is complete, eclipse continues to use the processor for a
> > while. Any ideas what is causing this?
> >
> >
> >
> > I'm using Eclipse 3.3M4 with the Mon, 29 Jan 2007 -- 11:23 (-0500) build
> > of the AJDT plugin.
> >
> > Regards,
> >
> >
> >
> > Kostas
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users