[
https://issues.apache.org/jira/browse/OOZIE-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13444644#comment-13444644
]
Hadoop QA commented on OOZIE-981:
---------------------------------
Testing JIRA OOZIE-981
Cleaning local svn workspace
{code}
----------------------------
+1 PATCH_APPLIES
CLEAN cleaned target directories
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch does adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient
annotations
+1 the patch does not modify JPA files
+1 TESTS
Tests run: 902
Tests failures: 1
Tests errors: 1
+1 DISTRO
+1 distro tarball builds with the patch
----------------------------
{code}
The full output of the test-patch run is available at
https://builds.apache.org/job/oozie-trunk-precommit-build/71/
> Subworkflow lib not found in classpath when parent workflow lib overwrites it
> -----------------------------------------------------------------------------
>
> Key: OOZIE-981
> URL: https://issues.apache.org/jira/browse/OOZIE-981
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 3.3.0
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: 3.3.0
>
> Attachments: OOZIE-981.patch
>
>
> OOZIE-567 addresses the bug mentioned in the title here - by adding the
> subworkflow libpath to the classpath in addition to parent workflow libpath.
> OOZIE-871 reverted this to avoid duplicate values, but the subworkflow
> libpath should not be overwritten by parent workflow's libpath. Hence,
> tackling this bug here.
> Existing testcase modified slightly to demonstrate the expected behavior.
--
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
