[
https://issues.apache.org/jira/browse/TUSCANY-3858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Nash resolved TUSCANY-3858.
---------------------------------
Resolution: Fixed
Fix Version/s: Java-SCA-1.6.2
For some reason, resource filters in the plugin execution configuration of the
pom don't work when building from the top level. The fix is to specify resource
filters in the build section of the pom instead.
Fixed in the 1.6.2 branch under revision r1089134 and in the 1.x trunk under
revision r1091729.
> Eclipse update site doesn't build correctly from a top-level build
> ------------------------------------------------------------------
>
> Key: TUSCANY-3858
> URL: https://issues.apache.org/jira/browse/TUSCANY-3858
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Tools
> Affects Versions: Java-SCA-1.6.1
> Reporter: Simon Nash
> Assignee: Simon Nash
> Fix For: Java-SCA-1.6.2
>
>
> When building the Eclipse update site as part of a top-level build, a number
> of files in the update site are incorrect because resource filtering isn't
> applied correctly. This causes the substitution variable
> ${tuscany.eclipse.version} to appear as a literal string in various xml
> files, manifest files and jar names instead of being replaced by a correct
> value such as 1.6.2.v20110405-1631.
> If the Eclipse update site is built from the tools/eclipse directory,
> everything works correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
