2.5.4 - 15 March 2005
Fixed a bug preventing the analysis of projects with cyclic dependencies.
2.5.3 - 10 September 2004
Optimized the incremental database update. Now when you change the code you don't
see a progress bar flash before your eyes.
2.5.2 - 1 August 2004
Ported to Eclipse 3.0.
- Removed some problematic features in the Projection View.
- Replaced highlighting of relations in the Java Editor by circular traversal of
all source code mapping a certain relation. If you keep single-clicking on a target node
in the Projection View or on a relation in the Relations view, the Java editor
will cycle between corresponding locations in the source code.
2.5.1 - 5 December 2003
Reverted to the Participants View of 2.4.0. Bug fixes:
- 101 - IO Exception when filenames have bad capitalization
- 108 - Participants View broken with Inconsistencies
- 111 - Fails to get dependent projects
- 112 - Dependent projects are not transitively included
- 113 - Creating a CG with a non-Java project raises an exception
2.5.0 - 25 September 2003
Important change to the Participants View. The new Participants
View combines information from both the Concern Graph View and the Relations View.
This allows you to use FEAT in the Java perspective without switching to the FEAT Perspective
most of the time.
- FEAT now supports browsing up and down the Concern Graph hierarchy within the
Participants View.
- The new Participants View displays both the participants and their relations.
- In the Participants View, a button supports hiding or showing the relations
for each participant.
- Fixed a problem with analyzing source code in the new version of Eclipse.
(ID: 57)
- Updated the documentation
- Supported auto updates
2.4.0 - August 5, 2003
Supports the analysis of code in dependent projects, concern building based
on code differencing, and many new features in the Participants and Projection Views.
- FEAT now supports the analysis of code in dependent projects. Packages
visible in the new concern graph wizard include code packages for all dependent
projects.
- FEAT supports automatically creating a concern capturing the additions to
a code base. After an initial database is created (when a concern is created
or loaded), in the Concern Graph View, select "Added Relations" and a new
concern will be created containing all the elements and relations in the
code base that were not in the initial code base (at load time).
- New query called "referenced-by".
- In the Participants and Projection views, a button allows you to filter out
all elements that are not part of the packages selected for analysis. The elements
are only filtered from the view, not the actual concern graph.
- In the Projection View, a button supports showing the transpose of the
current query results.
- In the Projection View, elements in the concern graph are annoted with a
small orange overlay.
- Tree expansion and collapsing have been changed to perform the expansion
and collapsing step-wise.
- Bug fixes: 48, 49, 51, 53, 54.
2.3.2 - July 3, 2003
This release is a patch over 2.3.1. No functionality added.
- Bug Fix: NullPointerException when multi-selecting a relation (ID: 46).
- Bug Fix: Extra semi-colon in analyzer (ID: 47).
2.3.1 - June 23, 2003
- FEAT Queries can now be performed from the Package Explorer and Outline View.
- Added support for adding a multiple selection to a concern from the
Package Explorer and the Projection View (ID: 28).
- Better expansion of query results in the Projection View (ID: 45)
- Better sorting in the Projection View: fields first, then methods,
then classes (ID: 27).
- Bug Fix: Missing parameter check in method compare (ID: 39).
- Bug Fix: Unnecessary database update on save (ID: 40).
- Bug Fix: Problem with limited open editors (ID: 41).
2.3.0 - May 27, 2003
This version of FEAT is much better integrated with the Java developement
environment.
FEAT Editor
The Code Viewer Area now displays the code relevant to parts of a
concern in an editable editor called the FEAT editor. Code relevant
to a concern is highlighted and marked with a marker on the right vertical
ruler.
In order to make sure FEAT works properly with
code highlighting, it is necessary to associate Java files with the FEAT Editor,
(in the properties page). The FEAT Editor supports all the original features of Java Editor
such as syntax highlighting and text hovering.
Automatic and Incremental Database Updates
FEAT detects any change to the source code of the project associated with a Concern Graph
and automatically updates the FEAT database to reflect the change. The update of the FEAT database
is incremental, and usually very fast. Updates to the source code can render a concern graph inconsistent
with the current version of the source code. Inconsistent concerns are marked with a red X in the
concern graphs view, and can be displayed in the Inconsistency View.
Preference Page
A FEAT section was added to the preference page. Users can customize the default concern
name and the preferred highlighting color for concerns.
UI Changes
- The progress monitor now shows the name of the source file being loaded.
- In most views, double-clicking on an element will show its declaration.
- Plugin information was added to the help about.
Bug fixes
Ids 26,34,36.
2.2.1 - April 24, 2003
Added support for tolerating inconsistencies between a concern graph
and the underlying source code, and support for reloading the FEAT
database when the code changes.
- Elements can be added when there is no concern graph created (ID:12)
- Source code reload button added (ID:13)
- Tree expand and collapse buttons added in Participants and Projection View.
- Bug fixes (ID:18,19,20,21,22,23,29,30,31)
- Updated the documentation.
2.2.0 - April 8, 2003
- New Eclipse native analyzer. This release does not rely on the JikesBT bytecode analyzer anymore.
- Added Save option for concern graphs (ID:7).
- Added scroll bars in the package list of the new Concern Graph wizard (ID:8)
- Added a check to prevent adding complex queries to a concern graph (ID:10)
- Removed context tracking (ID:11)
- Bug fix (ID: 16)
- Concern Graph creation wizard automatically launched when the user tries to add an element
and no concern graph is created (ID:12)
- Default name added in concern graph creation wizard (ID:14)
2.1.10 - March 5, 2003
Bug fixes which were causing problems with Eclipse 2.1. Improved tutorial.
2.1.9 - January 23, 2003
Contains a few bug fixes for 2.1.8, which was released a little early.
2.1.8 - January 20, 2003
- Bug fixed in the compare feature
- Interactions and Relations Views now refresh themselves automatically
- Improved the tutorial
- Added a description of the queries to the documentation
2.1.7 - January 8, 2003
- Added support for analyzing the default package (CR 31).
- Added a tutorial in the help (CR 32).
2.1.6
Addressed the following Change Requests:
- 22: Bug: Exception in Code Viewer
- 23: Bug: Exception in Code Viewer
- 24: Bug: Exception in Source Extractor
- 28: Add visual impact feedback in the Interactions View
2.1.5
Added a few relations and addressed the following Change Requests:
- 1: Class hierarchy does not seem to work.
- 2: Broken icons for next and previous buttons in Code View.
- 4: Attempt to create a Context View when opening a perspective.
- 5: Add sorting in the projection view.
- 8: Add specific title for Relation View
- 9: Support Concern Renaming
- 11: Subsumed relations are displayed twice
- 12: Null pointer exception in Code Viewer at line 92
- 18: Long names for method parameters not shown
- 20: Improve projector for implied relations
- 21: Views source for projection targets
2.1.4
First version officially stable enough to be released.