Installing your custom component automatically
You can follow specific rules to create a zip for your component so that the Studio can recognize and install your component automatically.
This approach is applicable only when you are using one of the subscription-based Talend solutions.
Creating the component zip
From the definition folder of the project,
in this example, execute the following commands sequentially to generate a
*-updatesite.zip file in the target
mvn clean package mvn package -DskipTests -DskipITs -PgenerateP2
Known issue: the
<classifier>bundle</classifier>line could be missing in the pom.xml file of this definition part, if you generated this pom file using Talend Archetype. In this case, before executing the above-mentioned commands, add manually this line between the
<instructions>tags of the maven-bundle-plugin artifact in this pom file.
For details of this known issue, see https://jira.talendforge.org/browse/TCOMP-627.
From the runtime folder of the project,
in this example, execute the following command.
mvn dependency:copy-dependencies -Dmdep.useRepositoryLayout=true -DoutputDirectory=target/plugin/m2/repository -DincludeScope=runtime -Dmdep.copyPom=false
This command generates the required dependencies in the target/plugin/m2/repository folder.
If you copy-paste this command from a PDF file, this command could have been broken into several lines. Restore this command into a single line before executing it.
Move this target/plugin/m2 folder to the root of the *-updatesite.zip file.
This makes the structure in the zip look like:
Adding the zip to the Studio
- Stop the Studio.
- Create a folder and name it to "patches" in the Studio installation directory.
- Move the *-updatesite.zip archive to this patches directory.
- Start the Studio. The Studio recognizes and installs your component automatically and displays a message about the successful installation.
- Create a Job to open the Palette. tGoogleFustionTableInput is now listed under the Cloud/Fusion Tables family.