gnodet commented on PR #8:
URL: https://github.com/apache/maven-executor/pull/8#issuecomment-4500918093
I see two ways forward:
**Solution 1 — `-parent` suffix on the current name**
Keep the project name as-is, but use `maven-executor-parent` as the parent
artifactId:
```xml
<groupId>org.apache.maven.executor</groupId>
<artifactId>maven-executor-parent</artifactId>
```
- No GA collision with the child `maven-executor` module
- Source-release zip is
`maven-executor-parent-${version}-source-release.zip` — clearly
Maven-identifiable
- `-parent` suffix is a well-established pattern
(`org.apache.maven:maven-parent` itself uses it)
**Solution 2 — Rename the project to something less vague**
If the real issue is that "executor" on its own is too generic, we could
rename the project. That would let the `G:G3` convention work with a
self-descriptive name. Three candidates:
| Project name | Parent GAV | Source-release zip |
|---|---|---|
| `maven-build-executor` | `o.a.m.buildexecutor:build-executor` |
`build-executor-${version}-source-release.zip` |
| `maven-runner` | `o.a.m.runner:runner` |
`runner-${version}-source-release.zip` |
| `maven-launcher` | `o.a.m.launcher:launcher` |
`launcher-${version}-source-release.zip` |
`maven-build-executor` is the lightest touch — keeps "executor" but
qualifies what's being executed, removing the `java.util.concurrent.Executor`
ambiguity.
_Claude Code on behalf of Guillaume Nodet_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
