You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Nash (JIRA)" <de...@tuscany.apache.org> on 2010/11/02 13:13:06 UTC
[jira] Created: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
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 number.
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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ 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 number.
> 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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927825#action_12927825 ]
Simon Nash commented on TUSCANY-3762:
-------------------------------------
The build.properties file for the core plugin needs to be updated to match these changes.
Updated in the 1.6.1 branch under revision r1030417 and in the 1.x trunk under revision r1030426.
> 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 number.
> 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.
[jira] Resolved: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Nash resolved TUSCANY-3762.
---------------------------------
Resolution: Fixed
Fixed under revisions r1030063 and r1030071 in the 1.6.1 branch and revisions r1030068 and r1030072 in the 1.x trunk.
> 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 number.
> 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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12930972#action_12930972 ]
Simon Nash commented on TUSCANY-3762:
-------------------------------------
As part of revision r1030063 (1.6.1 branch) and r1030068 (1.x trunk) a change in distribution/pom.xml that commented out some modules from the distribution build was checked in unintentionally.
This problem has been corrected under revisions r1033863 in the 1.6.1 branch and revision r1033866 in the 1.x trunk.
> 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 number.
> 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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932152#action_12932152 ]
Simon Nash commented on TUSCANY-3762:
-------------------------------------
In addition to the above changes, it's also necessary to do the following:
4. The files produced by applying filtering to the contents of the filtered-resources directories in tools/eclipse/features/core, tools/eclipse/plugins/core and tools/eclipse/site/updatesite need to be excluded from the source distribution. The original svn versions of these files that are located in the filtered-resources directories need to be included in the source distribution.
> 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 number.
> 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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931412#action_12931412 ]
Simon Nash commented on TUSCANY-3762:
-------------------------------------
After the last set of changes, the org.apache.tucsany.sca.core project can be imported into Eclipse but it produces errors from the Eclipse build about incorrect nesting of the "src" directory. The fix is to exclude the "src" directory from the resources listed in the pom.xml file.
Fixed under revision r1034402 in the 1.6.1 branch and revision r1034403 in the 1.x trunk.
> 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 number.
> 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.
[jira] Resolved: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Nash resolved TUSCANY-3762.
---------------------------------
Resolution: Fixed
Fixed under revisions r1035065, r1035066, r1035067, r1035075 and r1035254 in the 1.6.1 branch, and revisions r1035076, r1035077, r1035079, r1035081 and r1035413 in the 1.x trunk.
> 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 number.
> 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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931364#action_12931364 ]
Simon Nash commented on TUSCANY-3762:
-------------------------------------
The changes in revision r1030063 (1.6.1 branch) and r1030068 (1.x trunk) cause mvn eclipse:eclipse to fail on tools/eclipse/plugin/core with a message about a filtering conflict. The fix is to move the Java code in this module from the org/apache/tuscany/sca/core directory to a new directory src/main/java/org/apache/tuscany/sca/core.
Fixed under revisions r1034302, r1034303, r1034308 and r1034311 in the 1.6.1 branch and revisions r1034323, r1034328 and r1034331 in the 1.x trunk.
> 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 number.
> 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.
[jira] Reopened: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Nash reopened TUSCANY-3762:
---------------------------------
I'm reopening this issue because there are some problems with the previous changes made for this issue, as follows:
1. Running mvn eclipse:eclipse on tools/eclipse causes the timestamp in tools/eclipse/target/filter.properties to get updated which puts this file out of sync with the contents of the tools/eclipse/features/core and tools/eclipse/plugins/core submodules. If one of these submodules is then built without the other one being built, the core feature and core plugin will contain different build timestamps and they won't be compatible with each other.
The fix for this problem is to attach maven-antrun-plugin to a different phase in the pom.xml for tools/eclipse. It's currently attached to the generate-resources phase which means it automatically gets run by mvn eclipse:eclipse. Attaching it to the install phase instead of generate-resources solves the problem because it then doesn't get run by mvn eclipse:eclipse.
2. The build.properties file in tools/eclipse/plugins/core wasn't updated when the Java source code was moved to src/main/java in revision r1034302. This file is also missing the exsd/ directory (this isn't connected with the changes for TUSCANY-3762).
3. As a result of the previous changes for TUSCANY-3762, the build version timestamp is inserted into files in the feature and plugin jars using maven filtering instead of being a hard-coded value as it was previously. This works for the maven build but it doesn't work when the feature and plugin are imported into the Eclipse PDE. This is because the Eclipse PDE looks at some files in specific locations to determine the version number and build timestamp of the feature and plugin, so the correct information needs to appear in these places within the imported Eclipse projects.
The fix is to change how the build timestamp is filtered into the feature and plugin files, by placing all the files that need filtering in a new directory ${basedir}/filtered-resources and filtering these files as they are copied into the ${basedir} 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 number.
> 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.
[jira] Commented: (TUSCANY-3762) Tuscany SCA Eclipse plugin doesn't
install correctly
Posted by "Simon Nash (JIRA)" <de...@tuscany.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-3762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927376#action_12927376 ]
Simon Nash commented on TUSCANY-3762:
-------------------------------------
Some work has been done on a replacement update site / feature / plug-in as described in TUSCANY-2563. This has some refactoring improvements and is compatible with the current Eclipse software installer. The code for this is in the 1.x trunk under "tools/eclipse34" but it isn't in the build and has never been released, and it's not clear what state it's in.
For 1.6.1 I think it's too much work and too risky to try to get the "tools/eclipse34" version working and tested and switch over to using it. Instead I have made some changes to the current "tools/eclipse" version of the feature and plug-in that resolve the specific problems described in this JIRA.
For a future release we should re-evaluate whether to continue with "tools/eclipse" or change to using "tools/eclipse34".
> 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 number.
> 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.