[
https://issues.apache.org/jira/browse/UIMA-3080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709971#comment-13709971
]
Marshall Schor commented on UIMA-3080:
--------------------------------------
Until parent pom 7 is released, the individual plugins will need to override
this. Overriding is tricky, as maven does its own approach to merging things
within configuration elements. What I found works is to specify this as
follows:
* Add two empty <condition/> elements - these say there's nothing to be
added to any of the existing <condition> elements in the configuration
* Add the third <condition> element with the property spec and the right
test spec. Maven configuration merge will then add this element following the
first two.
{code}
<execution>
<id>BuildUpdateSite-pack-svnget-buildMetadata-commit-to-dev</id>
<configuration>
<target>
<condition /> <!-- don't add anything to the 1st condition element -->
<condition /> <!-- don't add anything to the 2nd condition element -->
<!-- insert this as the 3rd condition element -->
<condition property="apacheRelease">
<equals arg1="${isApacheRelease}" arg2="true" />
</condition>
</target>
</configuration>
</execution>
{code}
> ant test for apache-release not working for release for eclipse update site
> ---------------------------------------------------------------------------
>
> Key: UIMA-3080
> URL: https://issues.apache.org/jira/browse/UIMA-3080
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: parent-pom-6
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: parent-pom-7
>
>
> The test in the Eclipse update site to see if the apache release mode is true
> doesn't work as coded. Change to alternate form of testing maven property
> ${isApacheRelease} to be true.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
