Adding jars to the lib directory is not ideal as it pollutes all classloaders. We should add expression language support to the path property if it isn't already as that makes variable registry access available which makes use of the same template or flow in different environments easier.
On Aug 19, 2016 7:27 AM, "Peter Wicks (pwicks)" <[email protected]> wrote: Sumanth, If the driver is in your lib directory already then you should leave the path empty. All jar’s in your lib directory are loaded in the classpath for all NAR’s. Personally I have three different JDBC drivers in my lib directory to make them available for whoever needs them (MS SQL, SAP Hana, Teradata, and will add Oracle soon). --Peter *From:* Sumanth Chinthagunta [mailto:[email protected]] *Sent:* Thursday, August 18, 2016 8:56 PM *To:* [email protected] *Subject:* Re: adding dependencies like jdbc drivers to the build It would be nice if we support relative paths for driver jar. E.g., ./lib/mariadb-java-client-1.1.7.jar This let flow templet portable (dev -> prod) Sent from my iPhone On Aug 18, 2016, at 2:25 PM, Bryan Bende <[email protected]> wrote: For JDBC, if you are talking about the DBConnectionPool, you should be able to reference a driver as an external file such as file:///var/tmp/mariadb- java-client-1.1.7.jar' If you are talking about something different besides the DBConnectionPool then it depends what processor/component... If you look in the lib directory you will see all the NAR files, each NAR has one or more components along with all of the other JARs it needs, and each NAR has isolated class loading so that they will not interfere with each other. You would need to figure out which NAR you are dealing with and add a dependency to one of the poms related to that NAR. -Bryan On Thu, Aug 18, 2016 at 4:33 PM, Tom Gullo <[email protected]> wrote: If I want to add a jdbc driver or any third party dependency where should I add that dependency in the Maven build for Nifi? Thanks -Tom
