[
https://issues.apache.org/jira/browse/OOZIE-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614547#comment-13614547
]
Robert Kanter commented on OOZIE-670:
-------------------------------------
I haven't had a chance to try it out yet, but from a quick look, here's a minor
issue:
In the usage info, you have:
{code}
+ echo " prepare-war [-d directory] (-secure will configure the war
file to use HTTPS (SSL), and"
+ echo " [-d directory] will use alternative
directory other than libext"
+ echo " to process jar files)"
{code}
but in the documentation (which I think is the correct version), you have:
{code}
+ prepare-war [-d directory] [-secure]"
+ (-d identifies an alternative directory for processing
jars)"
(-secure will configure the war file to use HTTPS (SSL))"
{code}
These should be identical.
> Merge addtowar and oozie-setup scripts into one
> -----------------------------------------------
>
> Key: OOZIE-670
> URL: https://issues.apache.org/jira/browse/OOZIE-670
> Project: Oozie
> Issue Type: Improvement
> Reporter: Alejandro Abdelnur
> Assignee: Bowen Zhang
> Attachments: oozie-670.patch, oozie-670.patch, oozie-670.patch
>
>
> Same reasoning that OOZIE-669, this would simplify usage and documentation.
--
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
