integrate maven-executor Maven global view

[hboutemy]

Affected version

0.0.0

Bug description

we need to integrate this new component into full source tree https://maven.apache.org/scm.html
through https://github.com/apache/maven-sources/blob/master/default.xml
then in Maven site, either as a left menu entry (is this is a new "misc" or in /shared if it's a shared component)

Is this a shared component? is this a "misc"?
as said in apache/maven#12004, what about pre-existing maven-invoker and maven-verifier shared components?
I get that maven-executor what created for Maven ITs: I suppose its promotion outside Maven core makes a new expectation to use it outside just Maven ITs?

[hboutemy]

@cstamas any objection to make this maven-executor part of shared components?
= https://maven.apache.org/shared/index.html

it will ease promoting the transition in this index page
(I'm happy to help, of course)

[cstamas]

Sure. I explained that IMHO why not should be shared maven-executor (parallel to maven-enforcer), basically we deal with same thing here as in case of Enforcer: maven-executor is NOT meant to be a single library, will have more surrounding optional libraries and plugins. But I am fine to have something like one project producing different GAVs:

• shared/ the maven-executor and maven-batch-executor
• plugins/ the maven-executor-plugin
• ...

[hboutemy]

oh, now I get it: like Enforcer that produces components, plugin https://maven.apache.org/plugins/index.html and extension https://maven.apache.org/extensions/index.html

for executor, IIUC, for version 1 it produces only components https://github.com/apache/maven-executor/tree/executor-1.x, but in version 2 https://github.com/apache/maven-executor/tree/main it adds also a plugin and a CLI/tool https://maven.apache.org/tools/index.html = the batch side?

and replace 2 components for version 1: maven-verifier and maven-invoker
and in version 2 also replace some plugins like invoker plugin and/or verifier plugin?
(I'm even more interested in documenting/clarifying what we drop for lowering maintenance than what we add)

[hboutemy]

now that I get the plan, I'll make sure:

• we can publish the current 1.x SNAPSHOT https://github.com/apache/maven-executor/tree/executor-1.x to https://maven.apache.org/executor
• link maven-verifier and maven-invoker components to executor 1 for promoting the replacement

I know that creating https://maven.apache.org/executor with associated https://maven.apache.org/executor-archives always seems hard, because we don't do it often

[hboutemy]

https://github.com/apache/maven-site/pull/1574/changes#diff-1d32487f0e5db5e6d1426dd170cd4713a33d80b42d9fc5b7d52f0c9afab1108e is what has been missed for https://maven.apache.org/executor-archives = the public view of https://maven.apache.org/components/executor-archives
and when we are ready, publish the release doc https://maven.apache.org/developers/website/component-reference-documentation-helper.html?others