[
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.
