[jira] [Commented] (TUSCANY-3858) Eclipse update site doesn't build correctly from a top-level build

["Simon Nash (JIRA)" <de...@tuscany.apache.org>]

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

Simon Nash commented on TUSCANY-3858:
-------------------------------------

This seems to be caused by a problem with how Maven handles filter definitions. At present the filter definitions for the Eclipse update site modules are specified within the maven-resources-plugin execution configuration. If these definitions are moved to the <filters> element under the build section, the top-level build works correctly.

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