You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <ui...@incubator.apache.org> on 2009/10/02 00:42:23 UTC
[jira] Closed: (UIMA-1596) fix sandbox build - use of for
conditional not working for child projects
[ https://issues.apache.org/jira/browse/UIMA-1596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1596.
--------------------------------
Resolution: Fixed
> fix sandbox build - use of <profile> for conditional not working for child projects
> -----------------------------------------------------------------------------------
>
> Key: UIMA-1596
> URL: https://issues.apache.org/jira/browse/UIMA-1596
> Project: UIMA
> Issue Type: Bug
> Components: Build, Packaging and Test, Sandbox
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: 2.3S
>
>
> The SandboxDistr has common, factored-out build steps for the sandbox projects. One of this is to conditionally run the docbook build for the child project, if that project has a build_documentation.xml file.
> This was being done using a <profile> element in the factored-out Sandbox pom, which activated if that file was present.
> This works when you do mvn install from the child project; the <profile> is inherited via the <parent> chain, and all is well.
> However, if you run from the SandboxDistr (with the intent of running the build recurisvely on all the <module> children projects, this fails - because the <profile> is evaluated just once, for the SandboxDistr project.
> Fix this by abandoning this method of conditional execution, and reverting to <ant> conditional tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.