[OOZIE-1226] Workflow lib path not found in classpath for a subworkflow

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.3.2
• Labels: incompatible
• Assignee: Robert Kanter
• Reporter: Rohini Palaniswamy
• Created: 14/Feb/13 00:49
• Updated: 09/May/14 20:28
• Resolved: 15/Feb/13 06:14

Description

Currently only the jars in lib path of the subworkflow are added to classpath and the jars in lib path of the parent workflow are not.

History:
OOZIE-567 added support for adding subworkflow libpath to the classpath in addition to parent workflow libpath. OOZIE-871 had a change to avoid duplicate values, but caused the subworkflow libpath to be overwritten by parent workflow's libpath. OOZIE-981 caused the subworkflow libpath to be taken into account, but the parent workflow libpath was overwritten.