apache / apache/beam

Starter archetype pipeline has no runner on its classpath

Open
#18,067 0 comments 0 reactions 0 assignees View on GitHub
bug core java P3
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

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.

Imported from Jira [BEAM-1032](https://issues.apache.org/jira/browse/BEAM-1032). Original Jira may contain additional context.
Reported by: swegner.

Contributor guide

Open the contributing guide

Research direction

Inspect the starter archetype's Maven dependency configuration and compare it with the examples archetype, which includes the DirectRunner dependency. Run `mvn exec:java -Dexec.mainClass=swegner.StarterPipeline` with a generated project and verify that the pipeline starts without the missing-runner error.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.