Running a Batch

After using the batch wizard a new batch can be run automatically by selecting Run Immediately (see Creating a new batch). However, it is not necessary to fire up the wizard and repeat all of the selections every time you would like fresh class diagrams.

The batch wizard creates an AgileJ batch file called batch.ajb in a new folder called batch. There are two modes in which an existing batch file can be run.

Re-running and cleaning an existing batch

An existing batch can be cleaned and re-run from scratch to create a new collection of class diagrams reflecting the current state of the source code. In the package explorer, right click on the batch/batch.ajb file and select AgileJ StructureViews - Re-Run (clean) .

output folder

Running or resuming an existing batch preserving existing output

A partly run batch can be resumed. The batch process checks for existing output and continues by generating any missing files. This is useful for:

  • Picking up from where you left off with a batch which was stopped for some reason.
  • Re-running a batch after manually editing the class diagrams.

In the package explorer, right click on the batch/batch.ajb file and select AgileJ StructureViews - Run/Resume (preserve)

output folder

Stopping a Batch

A batch is an Eclipse job which can be halted just like any other Eclipse job. To kill the batch generator select

Window - Show View - Progress

In the list of running jobs will be AgileJ batch generator

Press the red square to end batch generation. This can be done safely at any time, the batch results so far generated will be retained, and if the batch is resumed then it will continue from where it was stopped.

Cleaning a batch

A batch can be cleaned and re-run without needing to start from scratch with the wizard. To clean a batch simply delete the uploadThis folder.

Java Heap

Batch processing is a relatively resource intensive operation involving the creation and retention of large inheritance and dependency trees. The easiest way to increase the memory available to Eclipse is to edit the eclipse.ini file. As a guide, a medium sized Java project requires about 500 MB to run to completion. A larger project may require 1 GB.

The eclipse.ini file is located in the same folder as the eclipse executable on Windows. On Mac OS X right click on the Eclipse.app file and select Show Package Contents which will open a new finder window with the eclipse.ini located under the Mac OS folder.

--launcher.XXMaxPermSize256m
-vmargs
-Xms40m
-Xmx512m

Note that it is important to avoid setting the -Xmx value greater than the physical memory available as this will only result in slow processing due to the use of paged memory and the postponement of Java garbage collection.

Copyright © AgileJ Ltd. All rights reserved.

AgileJ StructureViews is a plugin for Eclipse which generates UML class diagrams reverse engineered from Java source code.

Learn More

Stay Up To Date


Get In Touch

AgileJ Ltd
Trident Court, 1 Oakcroft Road
Chessington, Surrey
KT9 1BD
United Kingdom
+44 20 8123 2318