The goal is to provide a way to include extra artifacts embedded in the car produced by the talend-maven-plugin.
For instance, with connector azure-dls-gen2 the beam environment dependencies are scoped to provided.
That's fine for cloud environments but for studio, if the dependencies are not present in the m2 we will have some class loading issues.
First approach is to attach another car in the build process. We will still have the standard car (for docker connectors image) but a second one classified to another target (ie like studio).
Two possible solutions using mojo parameter:
- system property containing a list of extra artifacts
- system property pointing to a studio dedicated pom for filling extra deps
slack initial thread: https://talend.slack.com/archives/G2RLNU32P/p1626663684210000