We have several routines that require an external library/jar file.
We follow the instructions in the docs and upload these jars via the "Edit Routine Libraries" dialog on the routine. We have also tried the tLibraryLoad component specifying the same jar file.
This is all fine and dandy, but only for the developer who did this in their own studio.
When the changes are committed to SVN, no jar file is checked into the project. "svn status" shows no jars managed within the project that were uploaded by the developer in studio via the "edit routine libraries" dialog.
All other developers seem to have to repeat this manual process of locating the jar and referencing it in their studio
Even better, when we run this job via the Administration Center on a JobServer we get these kinds of errors
"!ENTRY org.talend.platform.logging 1 0 2016-05-04 16:19:42.128
!MESSAGE 2016-05-04 16:19:42,128 INFO org.talend.commons.exception.CommonExceptionHandler - missing jar:commons-lang3-3.4.jar"
What are we missing here? There has to be some way to have these jars available within the project or denoted as dependencies in your underlying build routines (i.e. maven artifacts etc). Is there not? How can we simply state the jar dependencies in our project and let every other developer get immediate access to them, same w/ the job servers.
Talend named a Leader.
Kickstart your first data integration and ETL projects.
Learn how to do cool things with Context Variables
Find out how to migrate from one database to another using the Dynamic schema
Pick up some tips and tricks with Context Variables