Hello everyone, After an unfortunate amount of manual inspection of feature dependencies and trial-and-error, I have managed to compose an itemization of software that is required in order to support a bundle install of Topcased 3.3.0 (i.e., a configuration with which org.topcased.sdk-3.3.0.zip and org.topcased.toolkit-3.3.0.zip content can actually be used). The "Topcased v3 Installation Guide" referenced by the Topcased 3.3.0 release notes (http://gforge.enseeiht.fr/docman/view.php/52/3700/Installation%20Guide%20v3 .pdf ) contains many omissions (and, I think, many inaccuracies).
Here is what I used (which is somewhat in line with content in the RCP distribution of Topcased 3.3.0): Eclipse SDK 3.5.1 EMF 2.5.0 (Includes XSD) EMF Validation 1.3.0 EMF Query 1.3.0 EMF Transaction 1.3.1 EMFT Compare (Incubation) 1.1.0 EMFT MWE (Incubation) 0.7.0 EMFT Search (Incubation) 0.7.0 GEF 3.5.1 GMF 2.2.1 M2M ATL 3.0.0 M2T Xpand 0.7.0 (This distro includes Xtend 0.7.0) MDT UML2 3.0.1 MDT OCL 1.3.0 Eclipse Monkey 1.0.0 (Terminated Project!) Mozilla Rhino 1.7.1 Acceleo 2.6.0 SmartQVT 0.2.1 A few notes and details on my discoveries while figuring this out: 1) The install guide states that Xpand, Xtend and MWE are only required for the Experimental Topcased bundles. This is not correct. These packages are called for by org.topcased.modeler.export.html, which is distributed with the non-experimental toolkit. 2) The install guide states EMFT Compare is optional. This is not correct. This package is called for by org.topcased.sam.requirements.core as well as org.topcased.sam.feature.group, both of which are distributed with the non-experimental toolkit. EMFT Compare is also documented as optional, but it is required as well. 3) For some reason, the distribution of Acceleo 2.6.0 that I obtained from the Acceleo project web site dumps two jar files in the features folder (org.acceleo and org.acceleo.exporter). I found that these were unnecessary, and can be removed (Eclipse produced errors attempting to process them, as it doesn't look like Eclipse 3.5.1 handles compressed/jar'ed feature info in the features folder by default). 4) The Mozilla Rhino software is now maintained under the Eclipse BIRT project. I couldn't find a means of downloading it separately, so I downloaded the BIRT Report Framework 2.5.1 distribution and pulled Mozilla Rhino 1.7.1 from it. The version of Rhino that is provided with the Topcased RCP distribution, v. 1.6.2, is several years old and, if obtained from the archived Eclipse Dash update site, is not being maintained there any longer. 5) Eclipse Monkey has been cycled through an end-of-life process with Eclipse.org. It is no longer developed/supported software: http://www.eclipse.org/project-slides/2008.08.13%20Monkey%20Termination%20Re view.pdf I would recommend to the Topcased team that they either seek alternatives to Eclipse Monkey, or take on the task of formally maintaining it and distributing it if it is to see continued use. No one at Eclipse.org has worked on Eclipse Monkey since mid-2007... Eclipse Monkey cannot be directly downloaded from Eclipse.org. It can either be pulled in from the legacy update site via P2: http://download.eclipse.org/technology/dash/update/ or extracted by hand from the Topcased RCP distribution. I hope this material can be used to support improvements going forward, -Pete ________________________________________________________ Pete Ellis Senior Member of the Technical Staff The WW Technology Group ________________________________________________________ _______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
