[ https://issues.apache.org/jira/browse/OOZIE-2795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978862#comment-15978862 ]
Abhishek Bafna edited comment on OOZIE-2795 at 4/21/17 3:42 PM: ---------------------------------------------------------------- [~gezapeti] If create the {{lib}} directory in {{distro.xml}} then it is affecting other logic which has been put into different scripts. The logic based on; if {{lib}} is not present, then create and copy the jars from {{WEB-INF/lib}}. Thanks. was (Author: abhishekbafna): [~gezapeti] Given that we are creating and copying the jars into lib directory {{src/main/assemblies/distro.xml}}. I think copying from WEB-INF into lib is not required. I tried it, after removing those steps from: {{client/src/main/bin/oozie}}, {{distro/src/main/bin/oozie-setup.sh}} and {{tools/src/main/bin/ooziedb.sh}}. The sharelib and start of the oozie service worked fine for me. Can you check that I did not miss anything here. Thanks. > 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 > Assignee: Peter Cseh > Attachments: OOZIE-2795-001.patch, OOZIE-2795-002.patch, > OOZIE-2795-003.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)