beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1032) Starter archetype pipeline has no runner on its classpath
Date Mon, 28 Nov 2016 21:31:58 GMT


ASF GitHub Bot commented on BEAM-1032:

Github user asfgit closed the pull request at:

> Starter archetype pipeline has no runner on its classpath
> ---------------------------------------------------------
>                 Key: BEAM-1032
>                 URL:
>             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

View raw message