Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
Vianney
Contributor III
Contributor III

Hard coded values in assembly.xml files

Hi,

I want to compile Talend jobs outside the Talend Open Studio, using the generated "pom" directory in project folder.

But with the TOS DI last version, 7.4.1M6, assembly.xml files contain hard coded values of local path instead of something like ${basedir}, making difficult the compilation process with Maven on another computer.

With new workspace, new project, new job, after the code generation :

C:\Talend\proj\TOS_DI-20201015_1726-V7.4.1M3\workspace\LOCAL_PROJECT\poms\jobs\process\job1_0.1\src\main\assemblies\assembly.xml

file contains :

   (...)

    <file>

      <source>

C:\Talend\proj\TOS_DI-20201015_1726-V7.4.1M3\configuration\.m2\repository

\org\dom4j\dom4j\2.1.3\dom4j-2.1.3.jar</source>

      <outputDirectory>lib</outputDirectory>

      <destName>dom4j-2.1.3.jar</destName>

     </file>

     <file>

      <source>

C:\Talend\proj\TOS_DI-20201015_1726-V7.4.1M3\configuration\.m2\repository

\org\slf4j\slf4j-api\1.7.25\slf4j-api-1.7.25.jar</source>

      <outputDirectory>lib</outputDirectory>

      <destName>slf4j-api-1.7.25.jar</destName>

     </file>

   (...)

Furthermore, those 2 libraries (dom4j-2.1.3.jar and slf4j-api-1.7.25.jar) are not required for the job execution.

2 questions :

  1. How to avoid those 2 hard coded directories ?
  2. Can it be corrected/variabilize in next TOS release ?

Thanks in advance,

Vianney

Labels (2)
1 Reply
NBhagat
Contributor
Contributor

I am facing the same issue with Talend 7.3.1. The assembly file inside POM folder is getting hardcoded path for common jar files like below when we run or build the job.

<file>

      <source>D:\TOS_ESB-20200219_1130-V7.3.1\Studio\configuration\.m2\repository\commons-beanutils\commons-beanutils\1.8.3\commons-beanutils-1.8.3.jar</source>

      <outputDirectory>lib</outputDirectory>

      <destName>commons-beanutils-1.8.3.jar</destName>

    </file>

    <file>

      <source>D:\TOS_ESB-20200219_1130-V7.3.1\Studio\configuration\.m2\repository\commons-beanutils\commons-beanutils\1.9.3\commons-beanutils-1.9.3.jar</source>

      <outputDirectory>lib</outputDirectory>

      <destName>commons-beanutils-1.9.3.jar</destName>

    </file>

 

Can anyone help what project configuration is missing due to which these hard coded path are coming and why these jar files are not included in <dependencySet><outputDirectory>lib</outputDirectory>?