[
https://issues.apache.org/jira/browse/OOZIE-976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryota Egashira updated OOZIE-976:
---------------------------------
Attachment: OOZIE-976-v3.patch
here is change.
- remove WFGEN.tar.gz (tomcat-bundled one), create only WFGEN.war
- change oozie-setup.sh such that WFGEN.war is deployed under
oozie-server/webapps/ (using the same oozie tomcat server) when user explicitly
copies WFGEN.war to libext directory (or user can manually dump WFGEN.war to
oozie-server/webapps/, which works). To avoid potential performance impact in
production system, as default, WFGEN.war is not deployed.
- WFGEN is not built as default (i.e., bin/mkdistro.sh). user can include build
of WFGEN by specifying profiles(bin/mkdistro.sh -PtestPatchCompile or
-PwfgenCompile). Test-patch jenkins job is using profile testPatchCompile
which builds WFGEN.
> add workflowgenerator into distro tarball
> -----------------------------------------
>
> Key: OOZIE-976
> URL: https://issues.apache.org/jira/browse/OOZIE-976
> Project: Oozie
> Issue Type: Sub-task
> Components: tools
> Affects Versions: 3.3.0, trunk
> Reporter: Ryota Egashira
> Assignee: Ryota Egashira
> Fix For: 3.3.0, trunk
>
> Attachments: OOZIE-976-v2.patch, OOZIE-976-v3.patch
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> to add workflowgenerator into distro tarball, it is needed to update
> top-level pom.xml and distro/pom.xml
--
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
