Details
-
Bug
-
Status: Patch Available
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
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:
$ 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
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:
#Create lib directory from war if lib doesn't exist
We could create a symlink to embedded-oozie-server/webapp/WEB-INF/lib/ or copy that directory.