Major Description
Currently, the oozie.libpath setting is allowed in job.properties when submitting a job to run in order to add a second directory to load jars from. It would be useful if the value of this setting set in the configuration of workflow actions were honored and the jars loaded.
The use case is that I have three existing Java apps each with their dependencies managed by Maven. To avoid dependency conflicts, I have to deploy their dependencies to three separate directories. What I would like to do is create a single workflow with three Java actions to execute the three jobs, but they each need their own setting for oozie.libpath.
Note: It may actually be oozie.launcher.oozie.libpath that should be configured within a workflow action. Either way, support for this functionality would be welcome.