Jean-Sebastien Delfino (JIRA) wrote:
Improve the Eclipse plugin/feature/site install and port it to Eclipse 3.4
--------------------------------------------------------------------------
Key: TUSCANY-2563
URL: https://issues.apache.org/jira/browse/TUSCANY-2563
Project: Tuscany
Issue Type: Improvement
Affects Versions: Java-SCA-Next
Reporter: Jean-Sebastien Delfino
Assignee: Jean-Sebastien Delfino
The Tuscany plugin/feature/site install doesn't play very well with Eclipse
3.4. Eclipse has changed their software update framework and Eclipse 3.4
complains that the Tuscany plugin is 'not compatible with the current
installation support' and has to launch the older update manager to install it.
Also the runtime zips are currently packaged with the Tuscany Eclipse feature, requiring a specific updatesite layout, and that's not in line with the Eclipse best practice, which is to package runtimes in plugins instead of features. This was just a point in time limitation as I was running into issues with the Maven assembly plugin when I put the update site together the first time. Since I'm going to make changes to the installer I want to fix that too.
Finally I'd like to have the plugin tooling code in a separate plugin from the
runtime, that'll also allow me to install different runtime options on top of
the base plugin.
I'm going to work on this in the next few days.
I'm starting to work on this. As a starting point I'm probably going to
put this in a tools/eclipse34 directory to avoid any breaks with the
current tools/eclipse modules.
I think the two can go in parallel for a while, in a second step, I'll
try to see if what I do under tools/eclipse34 can also work on 3.2 and 3.3.
--
Jean-Sebastien
