Skip to content

Allow specifying Main-Class in JavaCoordinator #67311

@uranusjr

Description

@uranusjr

Current JavaCoordinator implementation in #65958 uses JAR metadata Main-Class to identify the entry point. This requires the user to build the JARs in a certain way (only ONE specific JAR can have Main-Class). While this is a good default, we should also allow the coordinator to specify the main class to execute directly to provide more flexibility to users.

Metadata

Metadata

Assignees

Labels

AIP-108: CoordinatorChange this to an 'area:' label after AIP acceptance.area:corekind:featureFeature Requestspriority:mediumBug that should be fixed before next release but would not block a release

Type

No type
No fields configured for issues without a type.

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions