[mangrove-dev] Code Migration from STP-IM completed

[Adrian Mos <adrian.mos@xxxxxxxx>]

Hi all,

I have migrated all the code from STP-IM to Mangrove (renamed and refactored plugins and packages + copied everything).

You will now find it at:
host: dev.eclipse.org
repository: /svnroot/soa/org.eclipse.mangrove
method: svn+ssh

I have organized it according to the Magrove modules, here is a reminder of the names of the modules:
org.eclipse.soa.mangrove.core - the EMF core plugins

org.eclipse.soa.mangrove.branches - the Transformation Plug-ins (initial existing code in STP-IM): contain the logic required to move and convert information between editors, tools and the core metamodel instance.

org.eclipse.soa.mangrove.builder - ensures the constant updating of SOA artifacts in the core as well as in the corresponding editors and tools (e.g. when saving a diagram, update the appropriate artifacts in the core while also enabling the update of the corresponding artifact in related editors or tools).

org.eclipse.soa.mangrove.leaves - the Editor Extensions (initial existing code in STP-IM), extensions and improvements to editors and tools for adding Mangrove-specific functionality at design time (e.g. views allowing the enrichment of certain SOA elements in the core or configuration menus for customizing the amount of information to be moved to/from the core).

org.eclipse.soa.mangrove.roots - the Runtime Connections: plugins for moving information to and from runtime tools and repositories when needed in order to have a "living" core, providing a good reality snapshot. This can be useful when diagrams are out of sync or when aggregated monitoring information is required to update graphical elements. Also for generating deployment information in a common format.

Cheers,
Adrian.