The discoverer framework has been refactored to satisfy new requirements, including major simplifications for adopters and developers: discoverers are now easier to define and call programmatically.
All existing discoverer implementations have been migrated to this new framework, and old discoverer implementations have been deprecated.
Please consult the related documentation for more details on new features.
The browser now does more operations in the background, so that you can continue to interact with the UI while it is loading model elements or computing queries, customizations or facets
The workflow component was simplified by removing cruft.
The discoverer framework has been refactored to satisfy new requirements, including some simplification for adopters and developers. Existing discoverer implementations have be migrated to this new framework. Old discoverer implementations have been deprecated.
Some unnecessary limitations have been removed for calling the java discoverer from Java. It is now possible to specify a set of IJavaProject instances as input, whatever the dependencies between these java projects.
org.eclipse.modisco.java.generation.files.GenerateJavaExtended becomes the main public API. So Generate_JavaStructures is deprecated.
An additional discoverer parameter allows to indicate some path to a custom .asm file to use while transforming Java models to KDM models.
Discovery filters are improved using regular expressions for types and packages to exclude/include.
The corresponding code is then highlighted in a source editor:
We have added notion of discovery parameters in process. So it changes the api of Discoverer interface: method Resource discoverElement(Object source, URI target) is now deprecated and has been replaced by method void discoverElement(Object source, Map<DiscoveryParameter, Object> parameters). This new method is more generic and should be used in coordination with provided list of discovery parameters.
We provide also an abstract class AbstractDiscovererImpl to ease the development of new discoverers.
The launch configuration dedicated to discovery has been adapted to represent all discovery parameters and to edit their values (it only supports basic types, like primitive types and collections of Strings).
A MoDisco resource selection dialog is now available. This dialog avoids having to manually write the URI of the required resource (eg: "modisco:/query/myQuery").
To open this dialog, right-click and select Load MoDisco resource.
.
Extracted core functionality from the browser, so that it can be reused in other plug-ins (see UI Core). This makes it possible to embed model browsing functionality in any view. For example, plug-in infra.browser.uicore.examples.cnf demonstrates how to integrate the model browser in the Project Explorer (using the Common Navigator Framework) :
). This makes it easier to know whether two elements in the tree are equal.
The browser is now extensively customizable through the use of uiCustom files:
These customizations can be easily created using a dedicated editor]:
)
):
The browser components are now fully internationalization ready.
Eclipse Forms look:
Less often used options are moved to a sub-menu in each toolbar so as to avoid cluttering the UI.
A pop-up menu action helping to create a Java model query implementation class is now available. To use it right-click on a JavaModelQuery and use Create Java Query Implementation Class.
With notion of discovery parameters, driver for discoverers has been updated to reflect new kind of parameters.
A "Java Generation" plug-in is available. The aim is to provide Java code generation from a Java model. Such a generation will participate to Legacy Refactoring & Migration chains.
Java Discovery parameters are completed with a Java filter field which allows to exclude some Java packages from discovery. This feature will be convenient when dealing with a large amount of Java source in one single Java project.
initial version