cstamas commented on PR #8:
URL: https://github.com/apache/maven-executor/pull/8#issuecomment-4499272187
Q1: any proposal then, how to name the `maven-executor` module in existing
repo, given that this should be the parent now?
Q2: this will go against the "common practice" of `G1.G2.G3:G3` naming
schema (ie. `org.apache.maven:maven`) of reactors
Q3: (the only identified problem so far) Do we **really think** that
`maven-executor-${version}-source-release.zip` is a **must**, to identify a
release _within Maven project_? As IMO by this logic, everything in this
project should be "maven-this" and "maven-that", while the project umbrella off
all these files and artifacts is "ASF Maven"? Isn't this redundant? We are not
talking about "I found a file on my SSD and have no idea where it belongs (as
file name is not fully self-contained)", but about source bundle of a ASF Maven
subproject, that we all (and SVN structure) shows where it belongs.
--
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]
