mojohaus / mojohaus/exec-maven-plugin
exec:java should default to Main-Class manifest attribute if <mainClass> not specified
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 191
- Forks
- 111
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 4
Description
Granted, this is just a convenience feature, but having to manually specify a <mainClass> if the <executableDependency> already has a Main-Class manifest attribute seems redundant.
And yes, I realize that there may be multiple manifest candidates if no <executableDependency> is specified, but even limiting this to just the case where a <executableDependency> would be a usability win, IMHO.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the exec:java goal and its handling of and , then inspect how a dependency's manifest Main-Class is read. Done means exec:java uses that manifest entry when no is specified and an is present, with coverage for the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100