Deprecate project; users should go to maven-executor instead
Open
maintenance
- Dominant language
- Java
- Stars
- 22
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
### Affected version
all
### Bug description
The maven-executor drop in replacement should be use that among other things offer smooth and transparent mvn3 and mvn4 support and same if not more functionality as maven-invoker and much more, like proper env isolation and so on.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by reviewing the project and comparing its stated functionality with maven-executor, then determine the deprecation scope and communication needed; done means the project’s deprecation path is agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100