gnodet commented on code in PR #1965:
URL: https://github.com/apache/maven-resolver/pull/1965#discussion_r3594994953
##########
maven-resolver-tools/pom.xml:
##########
@@ -199,8 +204,8 @@
<phase>package</phase>
<configuration>
<mainClass>org.eclipse.aether.tools.CollectConfiguration</mainClass>
+ <classpathScope>test</classpathScope>
<arguments>
- <argument>--mode=resolver</argument>
<argument>--templates=configuration.properties,configuration.yaml</argument>
Review Comment:
Right, these are not used yet by any consumer that I'm aware of. The
original idea was to provide a machine-readable catalog of all configuration
keys so that external tools (IDE plugins, CLI helpers, etc.) could offer
auto-completion, validation, or contextual help for resolver/maven
configuration properties.
I still think it's a good idea to keep deploying them — they're cheap to
generate and having a stable, versioned catalog of configuration keys published
to Central makes it easy for tooling to pick them up whenever someone builds
that integration. The format is straightforward
(key/type/default/description/since), so it wouldn't be hard to consume.
That said, if we feel they add noise to the release, we could also consider
not attaching them as separate artifacts and instead embedding the properties
file inside the jar as a classpath resource (e.g.
`META-INF/maven-resolver/configuration.properties`). That would still make them
discoverable but without publishing extra artifacts.
--
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]
