You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Scott Wegner (JIRA)" <ji...@apache.org> on 2016/11/22 00:48:58 UTC
[jira] [Created] (BEAM-1032) Starter archetype pipeline has no
runner on its classpath
Scott Wegner created BEAM-1032:
----------------------------------
Summary: 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
Assignee: Scott Wegner
Priority: Minor
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
(v6.3.4#6332)