As per maven documentation, the "system" scope is similar to "provided"
scope. That means jre or platform is suppose to provide the jar at runtime.
Normally, Malhar library jar is included in uber jar and is not at provided
scope when we build an apa. That's why your application can't locate the
cl
I’m attempting to build a new application leveraging a custom Malhar library.
I’ve compiled the updated Malhar library, confirmed that the classes I’ve added
are present, and added this specific library as a system dependency in my pom
of the newly created application:
org.apache.apex
malh
