[jira] Commented: (TUSCANY-2563) Improve the Eclipse plugin/feature/site install and port it to Eclipse 3.4

["Jean-Sebastien Delfino (JIRA)" <de...@tuscany.apache.org>]

    [ https://issues.apache.org/jira/browse/TUSCANY-2563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12625118#action_12625118 ] 

Jean-Sebastien Delfino commented on TUSCANY-2563:
-------------------------------------------------

I've committed a first cut of the features, plugins, build scripts that ship the pieces of runtime in the plugins instead of the features and an Eclipse 3.4 compatible update site r688425.

I need to do some end to end testing with these plugins. I'll do that in the next few days.

Another work item is to automate the generation of the Eclipse 3.4 Ganymede repository metadata from the update site with the Maven build. It is currently in a etc/generate-p2.sh script, but Ganymede has an Ant task that could be integrated in the build. However I'm not sure if they have  made the bundle that contains it available for download in a Maven repository yet.

> 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
>             Fix For: Java-SCA-Next
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.