Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1

StefanE1 — Fri, 02 Jan 2026 14:45:42 GMT

Hi,

I have developed a processor component with the TaCoKit, which calculates hash values. The installation works in Talend Open Studio (7.2.1).

I have made the following observations:

The file STUDIO_HOME/configuration/components-registration.properties is referenced in the file STUDIO_HOME/configuration/config.ini. If, under Windows, a path is specified with double backslashes, the component is not loaded and no error message is displayed, not even in the log (STUDIO_HOME/workspace/.metadata/.log). If normal slashes (Unix notation) are used, then the component will load correctly.

Then I also tried to install the component in a full version of Talend Studio (DI 7.2.1), but it doesn't work, not even with the Unix notation in the path in config.ini.

The following exceptions may be related (from STUDIO_HOME/workspace/.metadata/.log):

java.lang.IllegalArgumentException: can't resolve 'org.talend.sdk.component:component-server:jar:1.1.14', in development ensure you are using maven.repository=global in configuration/config.ini, in a standalone installation, ensure the studio maven repository contains this dependency

at org.talend.sdk.component.studio.ServerManager.lambda$0(ServerManager.java:112)

at org.talend.sdk.component.studio.ProcessManager.createClasspath(ProcessManager.java:489)

at org.talend.sdk.component.studio.ProcessManager.start(ProcessManager.java:225)

at org.talend.sdk.component.studio.ServerManager.start(ServerManager.java:119)

[cut]

Caused by: java.io.IOException: Error resolving artifact org.talend.sdk.component:component-server:jar:1.1.14: [Could not find artifact org.talend.sdk.component:component-server:jar:1.1.14]

at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.configureIOException(AetherBasedResolver.java:830)

at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:801)

[cut]

Suppressed: shaded.org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact org.talend.sdk.component:component-server:jar:1.1.14

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:403)

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:215)

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:192)

at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:247)

at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:794)

... 28 more

Caused by: shaded.org.eclipse.aether.resolution.ArtifactResolutionException: Error resolving artifact org.talend.sdk.component:component-server:jar:1.1.14

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:413)

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:215)

at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:192)

at shaded.org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveArtifact(DefaultRepositorySystem.java:247)

at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:794)

... 28 more

and:

org.eclipse.core.runtime.CoreException: Plug-in "org.talend.sdk.component.studio-integration" was unable to instantiate class "org.talend.sdk.component.studio.metadata.handler.TaCoKitImportHandler".

at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:216)

at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:208)

at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:934)

at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:246)

[cut]

Caused by: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

at java.lang.reflect.Constructor.newInstance(Constructor.java:423)

at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:206)

... 57 more

Caused by: java.lang.NullPointerException: A null service reference is not allowed.

at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:625)

at org.talend.sdk.component.studio.Lookups.lookup(Lookups.java:142)

at org.talend.sdk.component.studio.Lookups.taCoKitCache(Lookups.java:132)

at org.talend.sdk.component.studio.metadata.handler.TaCoKitImportHandler.<init>(TaCoKitImportHandler.java:37)

... 62 more

With the first exception I noticed that the Maven coordinates look wrong, type and version seem to be mixed up.

Instead of 'org.talend.sdk.component:component-server:jar:1.1.14' it should be 'org.talend.sdk.component:component-server:1.1.14:jar'.

How can I proceed further to solve the problem?

Re: Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1

Lim — Wed, 10 Feb 2021 11:07:01 GMT

Hello @Stefan Eder

To include your component in studio, you just need to have a jar in studio's or your global .m2/repository and put maven coordinates into the config.ini file. There's no unix/windows file separators in the path for component.java.coordinates, it should be <groupId>:<artifactId>:<version>

Could you please clarify what is your own component version are you installing and what component-server dependency version is?

Re: Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1

undx — Wed, 10 Feb 2021 11:33:59 GMT

Hi @Stefan Eder ,

to install a custom component, please use the car file generated during the package maven phase or use the talend-component maven plugin.

For the car installation, have a look here :

https://talend.github.io/component-runtime/main/1.30.0/studio-from-car.html

For the plugin deploy from your ide or cli (adapt command-line to your studio) :

> mvn clean install talend-component:deploy-in-studio -Dtalend.component.studioHome=/home/undx/Work/TCOMP-1651/TalendStudio-7.3.1/studio/ -f pom.xml

On the startup issue, please can you specify the Studio full release version? Vanilla is using component-runtime version 1.1.10, latest patched 1.15.2.

The GAV information in logs is misleading as there's a specific transformation done before resolving the artifact. So, I'll say there's a provisioning issue and the artifact is missing.

topic Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1 in Talend Studio

Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1

Re: Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1

Re: Problems to install a TaCoKit component in the comercial version of Talend Studio DI 7.2.1