GitHub user shivanandullagaddi added a comment to the discussion: Missing essential files (pom.xml and App.java) required for Hop SDK configuration and successful pipeline execution
Hi @hansva this was the problem when i run the App.java mvn clean compile exec:java "-Dexec.mainClass=com.shiva.hopdemo.App" [INFO] Scanning for projects... [INFO] [INFO] -----------------------< com.shiva.hopdemo:demo >----------------------- [INFO] Building HopSDKDemo 1.0-SNAPSHOT [INFO] from pom.xml [INFO] --------------------------------[ jar ]--------------------------------- [INFO] [INFO] --- clean:3.2.0:clean (default-clean) @ demo --- [INFO] Deleting C:\Users\shiva\OneDrive\Desktop\demo\target [INFO] [INFO] --- resources:3.3.1:resources (default-resources) @ demo --- [INFO] skip non existing resourceDirectory C:\Users\shiva\OneDrive\Desktop\demo\src\main\resources [INFO] [INFO] --- compiler:3.13.0:compile (default-compile) @ demo --- [INFO] Recompiling the module because of changed source code. [INFO] Compiling 1 source file with javac [debug target 17] to target\classes [INFO] [INFO] --- exec:3.1.0:java (default-cli) @ demo --- Initializing Apache Hop Environment... Hop configuration file not found, not serializing: C:\Users\shiva\OneDrive\Desktop\demo\config\hop-config.json SLF4J: Class path contains multiple SLF4J providers. SLF4J: Found provider [org.slf4j.nop.NOPServiceProvider@10e8a8f5] SLF4J: Found provider [ch.qos.logback.classic.spi.LogbackServiceProvider@4310f342] SLF4J: See https://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual provider is of type [org.slf4j.nop.NOPServiceProvider@10e8a8f5] ? Loading pipeline: C:/Users/shiva/Downloads/apache-hop-client-2.15.0/hop/config/projects/default/pipelines/pipeline_example_1.hpl ? Hop Exception: API error: metadata provider can't be null. When loading a pipeline Hop needs to be able to reference external metadata objects org.apache.hop.core.exception.HopXmlException: API error: metadata provider can't be null. When loading a pipeline Hop needs to be able to reference external metadata objects at org.apache.hop.pipeline.PipelineMeta.<init>(PipelineMeta.java:1658) at com.shiva.hopdemo.App.main(App.java:45) at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:279) at java.base/java.lang.Thread.run(Thread.java:840) [WARNING] thread Thread[Timer-0,5,com.shiva.hopdemo.App] was interrupted but is still alive after waiting at least 15000msecs [WARNING] thread Thread[Timer-0,5,com.shiva.hopdemo.App] will linger despite being asked to die via interruption [WARNING] NOTE: 1 thread(s) did not finish despite being asked to via interruption. This is not a problem with exec:java, it is a problem with the running code. Although not serious, it should be remedied. [WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=com.shiva.hopdemo.App,maxpri=10] java.lang.IllegalThreadStateException at java.lang.ThreadGroup.destroy (ThreadGroup.java:803) at org.codehaus.mojo.exec.ExecJavaMojo.execute (ExecJavaMojo.java:319) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:328) at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:316) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:174) at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:75) at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:162) at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39) at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:159) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261) at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173) at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101) at org.apache.maven.cli.MavenCli.execute (MavenCli.java:906) at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:283) at org.apache.maven.cli.MavenCli.main (MavenCli.java:206) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method) at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:77) at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke (Method.java:569) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:255) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:201) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:361) at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:314) [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 21.340 s [INFO] Finished at: 2025-11-06T15:58:51+05:30 [INFO] ------------------------------------------------------------------------ And coming to this point: You will also need to include each and every transform that your pipeline executes and its dependencies. where we can have it? any sample guide GitHub link: https://github.com/apache/hop/discussions/5960#discussioncomment-14894438 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
