tuscany-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simon Nash (JIRA)" <...@tuscany.apache.org>
Subject [jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't install correctly
Date Tue, 02 Nov 2010 12:56:25 GMT

    [ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927384#action_12927384

Simon Nash commented on TUSCANY-3762:

The problem with uninstall seems to be directly related to using the older Update Manager.
 We're using this currently because it has the facility to customize the install by copying
additional files (the Tuscany runtime and source distributions) into the Tuscany feature directory.
These additional files aren't packaged within the feature itself but are downloaded from the
Tuscany distribution site.

Unfortunately the current Eclipse software installer doesn't support copying these additional
files so it's necessary to find another way to install these files as part of the feature.
The chosen solution is to package these files as part of the feature.  This makes the feature
much larger but it doesn't increase the amount of data that needs to be downloaded when the
feature is installed. It also doesn't increase the size on disk of the installed feature on
the user's machine. It does increase the amount of space needed on the Tuscany distribution
site for a Tuscany release by about 70MB, and it also increases the time taken to upload a
Tuscany release candidate or release.

The approach taken to implement this new packaging is as follows:

1. The top-level build bulds the tools/eclipse directory. This automatically generates a timestamp
for the build which is used by the build to construct the Eclipse version number of the feature
and plug-in. This step builds the feature, plug-in and update site, though these are not yet
in their final deployable form and need to be completed by step 2 below.

2. The distribution build takes the Eclipse feature as built by step 1 above and repackages
it to add the binary distribution files (excluding demos/samples/tutorials) and the source
distribution zip file. It adds this to the update site created by step 1 and places the resulting
deployable final form of the update site in the distribution/target directory.

> Tuscany SCA Eclipse plugin doesn't install correctly
> ----------------------------------------------------
>                 Key: TUSCANY-3762
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3762
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Tools
>    Affects Versions: Java-SCA-1.6
>            Reporter: Simon Nash
>            Assignee: Simon Nash
>             Fix For: Java-SCA-1.6.1
> When installing the Tuscany SCA Eclipse feature and plugin from the Eclipse update site,
there are a number of problems as follows:
> 1. The Tuscany SCA Eclipse feature installation isn't compatible with the current Eclipse
software installation and update mechanism in Eclipse 3.4 and above. This forces a switch
to the older Update Manager which requires the update site information to be re-entered.
> 2. After the installation completes, the Eclipse installed software window doesn't have
an entry for Tuscany in the Installed Software or Features tabs. Tuscany is shown only in
the Plug-ins tab.
> 3. It isn't possible to uninstall the Tuscany SCA Eclipse feature.  The Tuscany feature
and plugin directories can be deleted from Eclipse manually but this doesn't remove the Tuscany
plug-in from the list of installed plug-ins.
> 4. The version number of the Tuscany SCA Eclipse feature and plug-in doesn't conform
to Eclipse format conventions which require a timestamp following the release number.
> 5. It's not possible to install and test the Tuscany SCA Eclipse feature when it's built
from the trunk or from a release branch because Eclipse can't handle n.n.n-SNAPSHOT as a version
> 6. The Tuscany SCA Eclipse feature and plug-in don't conform to Eclipse conventions for
displaying copyright and license information when they are installed.

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

View raw message