<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Maven plugin to support Jet based component development in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Maven-plugin-to-support-Jet-based-component-development/m-p/2253690#M148698</link>
    <description>&lt;P&gt;First of all: I am a fan of the jet based components because they are clear to understand and create easy to understand job code AND I am sure they providing much better performance than the new component development framework SDK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To support this development I have created (actually 3 years ago) a public available maven plugin which helps&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;update the component XML file&lt;/LI&gt;&lt;LI&gt;take care the jars needed for the component&lt;/LI&gt;&lt;LI&gt;checks also the message property files for missing keys&lt;/LI&gt;&lt;LI&gt;copies the component to the custom component folder&lt;/LI&gt;&lt;LI&gt;create a label in the advanced settings to show the component version and build date in the studio&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This plugin is described here: &lt;A href="https://github.com/jlolling/talendcomp_maven_plugins" target="_blank"&gt;https://github.com/jlolling/talendcomp_maven_plugins&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You can simply add it to your maven pom and it will be downloaded from maven central&lt;/P&gt;</description>
    <pubDate>Fri, 02 Jan 2026 14:45:42 GMT</pubDate>
    <dc:creator>jlolling</dc:creator>
    <dc:date>2026-01-02T14:45:42Z</dc:date>
    <item>
      <title>Maven plugin to support Jet based component development</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Maven-plugin-to-support-Jet-based-component-development/m-p/2253690#M148698</link>
      <description>&lt;P&gt;First of all: I am a fan of the jet based components because they are clear to understand and create easy to understand job code AND I am sure they providing much better performance than the new component development framework SDK.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To support this development I have created (actually 3 years ago) a public available maven plugin which helps&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;update the component XML file&lt;/LI&gt;&lt;LI&gt;take care the jars needed for the component&lt;/LI&gt;&lt;LI&gt;checks also the message property files for missing keys&lt;/LI&gt;&lt;LI&gt;copies the component to the custom component folder&lt;/LI&gt;&lt;LI&gt;create a label in the advanced settings to show the component version and build date in the studio&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;This plugin is described here: &lt;A href="https://github.com/jlolling/talendcomp_maven_plugins" target="_blank"&gt;https://github.com/jlolling/talendcomp_maven_plugins&lt;/A&gt;&lt;/P&gt;&lt;P&gt;You can simply add it to your maven pom and it will be downloaded from maven central&lt;/P&gt;</description>
      <pubDate>Fri, 02 Jan 2026 14:45:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Maven-plugin-to-support-Jet-based-component-development/m-p/2253690#M148698</guid>
      <dc:creator>jlolling</dc:creator>
      <dc:date>2026-01-02T14:45:42Z</dc:date>
    </item>
    <item>
      <title>Re: Maven plugin to support Jet based component development</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Maven-plugin-to-support-Jet-based-component-development/m-p/2253691#M148699</link>
      <description>&lt;P&gt;Hello Jan,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for sharing your plugin for Javajet based components.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The new &lt;A href="https://talend.github.io/component-runtime/main/latest/" alt="https://talend.github.io/component-runtime/main/latest/" target="_blank"&gt;Talend Component Kit&lt;/A&gt; based components do have a small overhead due to serialization/deserialization between the studio generated code and the framework. However the functionalities that the framework itself provide compensate for this. In other words the overhead shouldn't be concerning.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When using the new framework:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Dependencies are managed in the maven pom file&lt;/LI&gt;&lt;LI&gt;Jars are linked to component families&lt;/LI&gt;&lt;LI&gt;Messages.properties content is checked using the validation check: https://talend.github.io/component-runtime/main/latest/build-tools-maven.html#_validating_the_component_programming_model&lt;/LI&gt;&lt;LI&gt;Automatically generates a component.car file that contains all the dependencies and the installer to install the component.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;However by default it does not have the label in studio under the Advanced settings.  (Although this is something we could improve.)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I do also very much like JavaJet, but I strongly advocate to give a try to the component kit. Having all the test functionality, the ability for the dynamic UI elments, not to mention that one can have Guess Schema and a Metadata entry and the UI configuration changes can be managed from the component itself. These weren't possible with Javajet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I could go on however I was mostly focusing on the pain points you have to solved in your Javajet based developments with your plugin.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2022 01:42:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Maven-plugin-to-support-Jet-based-component-development/m-p/2253691#M148699</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-12-08T01:42:21Z</dc:date>
    </item>
  </channel>
</rss>

