-
Notifications
You must be signed in to change notification settings - Fork 17.1k
Allow specifying Main-Class in JavaCoordinator #67311
Copy link
Copy link
Open
Labels
AIP-108: CoordinatorChange this to an 'area:' label after AIP acceptance.Change this to an 'area:' label after AIP acceptance.area:corekind:featureFeature RequestsFeature Requestspriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
Milestone
Metadata
Metadata
Assignees
Labels
AIP-108: CoordinatorChange this to an 'area:' label after AIP acceptance.Change this to an 'area:' label after AIP acceptance.area:corekind:featureFeature RequestsFeature Requestspriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
Backlog
Current JavaCoordinator implementation in #65958 uses JAR metadata
Main-Classto identify the entry point. This requires the user to build the JARs in a certain way (only ONE specific JAR can haveMain-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.