[
https://issues.apache.org/jira/browse/OOZIE-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13588592#comment-13588592
]
Robert Kanter commented on OOZIE-1233:
--------------------------------------
The javac warnings are not from my patch (no java code changes)
They are both just more duplicates of WARNINGs that already appear multiple
times related to maven:
[WARNING] Could not transfer metadata asm:asm/maven-metadata.xml from/to
local.repository (file:../../local.repository/trunk): No connector available to
access repository local.repository (file:../../local.repository/trunk) of type
legacy using the available factories WagonRepositoryConnectorFactory
> Add ability to configure Oozie to use HTTPS (SSL)
> -------------------------------------------------
>
> Key: OOZIE-1233
> URL: https://issues.apache.org/jira/browse/OOZIE-1233
> Project: Oozie
> Issue Type: New Feature
> Components: security
> Affects Versions: trunk, 3.3.2
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Attachments: OOZIE-1233.patch, OOZIE-1233.patch, OOZIE-1233.patch
>
>
> It's currently possible to configure Oozie to use HTTPS (SSL), but:
> # There isn't a standard way of configuring it
> # It can involve editing settings that users normally don't, including web.xml
> # There's no documentation; using a self-signed certificate with the Oozie
> client is particularly tricky
> We should add an argument to the oozie-setup.sh script that'll configure
> Oozie to use HTTPS so that its easy to do and there's a standard way that
> users will do it.
--
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
