Community
Participate
Working Groups
Since there have been so many changes in the way we've done things (preference settings, builder id etc.) since AJDT 1.1.12 we need a wizard to perform these operations for people when they install the new version of AJDT
The issues which need to be covered are: 1) Rename file extensions - java files should only contain java source, and aspects should be contained in .aj files. A lot of the functionality (Cross reference view etc.) depends on aspects being in .aj files which is why people need to update this. 2) the builder id has changed from org.eclipse.ajdt.ui.ajbuilder to org.eclipse.ajdt.core.ajbuilder. This needs to be updated and if people no longer wish to share their projects with older versions of AJDT, then the old builder id needs to be removed. 3) To reduce the size of plugin dependencies, we've moved aspectjrt.jar to it's own plugin org.aspectj.runtime (rather than requiring a dependency on org.aspectj.ajde). This needs to be switched unless people really do require a dependency on org.aspectj.ajde. 4) Workbench settings - in the past we have required people to change various workbench settings (one of which being turnign off red squiggles). We need to reset these. We also need to ensure that previous settings (compiler settings - outjar etc.) are preserved. 5) Cross Reference View - this replaces the cross cutting info being displayed in the outline view. We need to make people aware of it and so bring up the view. All this functionality existed in the code base as part of previous Configuration wizards and file conversion wizards. What has happened is for this all to be put in a central place. All the classes can be found within the org.eclipse.ajdt.internal.ui.wizards.migration package. The biggest issue was when to have the migration wizard appear. For timing reasons it was decided to put this code in BuildConfigurator.selectionChanged (..). Under the right circumstances, this makes a call to AJDTUtils.migrateWorkbench() which sets off the wizard. The circumstances under which the migration wizard appears are: - previous version of AJDT has been installed and - we've not run the migration wizard before for this workspace and - we're not a brand new workspace When the wizard doesn't appear: - brand new installation of AJDT (no previous ones) - brand new workspace irrespective of whether previous versions of AJDT have been installed There is also a flag to force the migration wizard to appear which can be used in testing and debugging the wizard. This flag is AJDTUtils.FORCE_MIGRATION and should be set to "true" if you want to test/debug the wizard. The wizard is available in the AJDT rc1 build.
