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

Announcements
Streamlining user types in Qlik Cloud capacity-based subscriptions: Read the Details
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Full Maven Integration

Hi,

 

Currently, I work on Continuous Integration for Talend Project. I use tools supplied by Talend solution: CI Builder, CommandLine, TAC and Nexus. The main flow seems to work, but I have an issue about Maven integration in project. 

 

My context:

Some routine in my project uses external modules to work. These modules are added to Talend Studio through Talend studio module management. All these modules are finally installed in folder located here:

<TalendStdioPath>/configuration/.m2/org/talend/libraries/

All these libraries are available on official maven repositories or on my company repositories.

To work  with Talend Continuous Integration solution, I had to copy all the libraries in the same folder of CommandLine.

 

My need:

  • How can I integrate Maven dependency in my project to resolve all dependencies through Maven engine and not by CommandLine/Studio engine ?
  • How can I specify Maven dependencies for my routines instead of External Module ? How can I generate corresponding Maven pom for my Continuous Integration life-cycle? 

I hope my description is clear. 

 

Regards 

 

Labels (3)
13 Replies
navds
Creator II
Creator II

Thanks, Sabrina.
I see that the ticket has been closed, isn't it? Where should I learn how to use the new feature then?

Regards,
Anonymous
Not applicable
Author

Hello,

This issue is fixed in V 7.0.1. I don't find any documentation about it and will check it with our R&D and DOCT team later 

Have you tried to setup a custom maven uri directly instead of a fixed jar name in the routine dependency in V 7.0.1?

Best regards

Sabrina

 

birari
Contributor II
Contributor II

Can you explain , what you have done. I am also facing same issue

vharcq
Contributor III
Contributor III

Good 🙂

The other option is to add depedencies on each end every routines by then you got very big build of every jobs because all is included.

I was looking for compile-time only dependencies on routines/beans level and up to 6.5.1 this is the best option