Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Talend Cloud AWS EU Scheduled Outage: Starting Tues 26 May 21:00 CEST with expected completion Wed 27 May 01:00 CEST
cancel
Showing results for 
Search instead for 
Did you mean: 
RLoushin
Contributor
Contributor

Talend CI Builder and consolidating jars

I use the Talend CI Builder command  line and run the generateAllPoms command to generate the poms for each job in my Talend project.

I then run a 'mvn package' to build/compile my code.

Both of these commands work fine and get me what I want.  However, I would like to make it more efficient.  

PROBLEM

The problem I have is that each Talend job gets its own set of dependent jar files.  So if I have 10 jobs I'm building, and each job uses the same jar, then that jar is downloaded 10 times.  Downloading the same jars over and over leads to a longer build time, and a final artifact that has dozens/hundreds of duplicate files and is very large in size.

WHAT I AM TRYING TO ACHIEVE

I would like to only have one central lib/ folder where all jars get downloaded to.  If 10 jobs all use a particular jar, then the jar will only be downloaded once and the jobs will just point to that jar location. 

Anyone know how I can go about accomplishing this?  I am guessing I would have to modify something in the default assembly or project xml...but I'm not exactly sure what that would be.

Labels (3)
0 Replies