You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Cseh (JIRA)" <ji...@apache.org> on 2017/02/11 21:11:41 UTC

[jira] [Updated] (OOZIE-2795) Create lib directory or symlink for Oozie CLI during packaging

     [ https://issues.apache.org/jira/browse/OOZIE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Cseh updated OOZIE-2795:
------------------------------
    Attachment: OOZIE-2795-001.patch

Attaching one possible fix.

There are other references for the oozie war file in scripts, I think they should also be checked:
{noformat}
 [191] 22:03 : oozie (master) :: ack "oozie.war"
distro/src/main/bin/addtowar.sh
22:  tmpDir=/tmp/oozie-war-packing-$$
25:  tmpWarDir=${tmpDir}/oozie-war
327:  #Inject the library in oozie war
355:  #Inject the SSL version of web.xml in oozie war
363:zip -r oozie.war * > /dev/null
368:cp ${tmpWarDir}/oozie.war ${outputWar}

distro/src/main/bin/oozie-setup.ps1
111:    $InputWar = "$OOZIE_HOME\oozie.war"
112:    $OutputWar = "$OOZIE_HOME\oozie-server\webapps\oozie.war"
181:        #Inject the SSL version of web.xml in oozie war

distro/src/main/bin/oozie-setup.sh
55:  tmpDir=/tmp/oozie-war-packing-$$
58:  tmpWarDir=${tmpDir}/oozie-war

distro/src/main/bin/oozied.cmd
81:  if NOT EXIST "%CATALINA_BASE%\webapps\oozie.war" call setup

tools/src/main/bin/ooziedb.sh
47:  unzip ${BASEDIR}/oozie.war WEB-INF/lib/*.jar -d ${BASEDIR}/lib > /dev/null


{noformat}

> Create lib directory or symlink for Oozie CLI during packaging
> --------------------------------------------------------------
>
>                 Key: OOZIE-2795
>                 URL: https://issues.apache.org/jira/browse/OOZIE-2795
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Attila Sasvari
>         Attachments: OOZIE-2795-001.patch
>
>
> After creating an Oozie distro, lib directory is not present in the distro directory (e.g. oozie-4.4.0-SNAPSHOT) in the generated tar.gz .
>  
> As a consequence, first run of theOozie CLI will fail if one tries to execute it prior to server start:
> {noformat}
> $ bin/oozie
> unzip:  cannot find or open /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war, /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.zip or /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/oozie.war.ZIP.
> mv: rename /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib/*.jar to /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/*.jar: No such file or directory
> rmdir: /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF/lib: No such file or directory
> rmdir: /Users/asasvari/workspace/apache/oozie/distro/target/oozie-4.4.0-SNAPSHOT/lib/WEB-INF: No such file or directory
> Error: Could not find or load main class org.apache.oozie.cli.OozieCLI
> {noformat}
> If you start the server first however, a symlink is created (see {{bin/oozie-jetty-server.sh}}), and this error will not be visible.
> Earlier {{bin/oozie}} created this library by extracting it from the WAR file used for Tomcat. Comment in the script:
> {noformat}
> #Create lib directory from war if lib doesn't exist 
> {noformat}
> We could create a symlink to embedded-oozie-server/webapp/WEB-INF/lib/ or copy that directory. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)