[
https://issues.apache.org/jira/browse/BEAM-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546181#comment-17546181
]
Kenneth Knowles commented on BEAM-1032:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18067
> Starter archetype pipeline has no runner on its classpath
> ---------------------------------------------------------
>
> Key: BEAM-1032
> URL: https://issues.apache.org/jira/browse/BEAM-1032
> Project: Beam
> Issue Type: Bug
> Components: sdk-java-core
> Reporter: Scott Wegner
> Priority: P3
> Labels: Clarified
>
> When generating a new maven project using the starter archetype, the pipeline
> does not execute because it doesn't have a runner jar on it's classpath:
> $ mvn exec:java -Dexec.mainClass=swegner.StarterPipeline
> ...
> [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:java
> (default-cli) on project yo: An exception occured while executing the Java
> class. null: InvocationTargetException: No Runner was specified and the
> DirectRunner was not found on the classpath.
> In the examples archetype, we have the direct runner as a dependency. We
> should do the same for the starter archetype.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
