Wrong classpath for sub-workflow #596

lfrancke opened this Issue Mar 15, 2011 · 0 comments


None yet
1 participant

We've got a parent-workflow A which includes a lib/ directory with some jars in it. If we start a sub-workflow B this new workflow gets the wrong classpath (according to the log "java.class.path" output).

If there are any files in A/lib B will only have A/lib on its classpath.
Only if A/lib is empty then B/lib will be picked up.

I can provide logs etc. if needed. This is with Oozie 2.2.1+82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment