[aspectj-dev] Beginning the extension of jdt.core in CVS

[Adrian Colyer <adrian_colyer@xxxxxxxxxx>]

I've just committed the first phase
of org.eclipse.jdt.core extension into the AspectJ CVS repository. This
change pushes AjParser and AjScanner down into shadows/org.eclipse.jdt.core
on branch aj_v_396. A new class DeclarationFactory in org.aspectj.ajdt.core
handles the creation of AspectJ-specific types to avoid creating circular
dependencies between the jdt and ajdt projects.

I made a couple of changes to the module
structure to accomodate this...

In HEAD:

Project org.aspectj.ajdt.core depends
on project org.eclipse.jdt.core as before
Project org.eclipse.jdt.core contains
and exports only the jars that result from building the shadow version
of org.eclipse.jdt.core (as before). However, this project has a new dependency
on a new module shadows.org.eclipse.jdt.core, and an external builder configured
to update its jars.
Project shadows.org.eclipse.jdt.core
contains a dummy build.xml file that presents a build target make.jdtcore.jar,
that simply echos a message to the console.

In BRANCH aj_v_396
Is the project shadows/org.eclipse.jdt.core
(as before).  Use the eclipse CVS project option "check out as..."
to check this project out as "shadows.org.eclipse.jdt.core"

The result of this setup is that developers
working from HEAD can continue as before (with the new module checked out),
developers working on the branch should not check out shadows.org.eclipse.jdt.core
from head, but instead check out the shadows/ version (using check out
as). This then enables a development mode whereby work can be done in the
shadows project, which will be picked up by a build of the org.eclipse.jdt.core
project. The org.aspectj.ajdt.core project depends on the built jars, not
the shadows project. The setup enables the AspectJ test suite to be continually
run against the file set that will be picked up by the cruise control build,
and updates of jars happen as painlessly as possible.

-- Adrian
Adrian_Colyer@xxxxxxxxxx