[GitHub] [maven] cstamas commented on pull request #1224: [MNG-7870] Undeprecate G level metadata

2023-09-06 Thread via GitHub


cstamas commented on PR #1224:
URL: https://github.com/apache/maven/pull/1224#issuecomment-1708247331

   ping?


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [maven] cstamas commented on pull request #1224: [MNG-7870] Undeprecate G level metadata

2023-09-06 Thread via GitHub


cstamas commented on PR #1224:
URL: https://github.com/apache/maven/pull/1224#issuecomment-1707871954

   And finally, i find this page (rendered as part of maven-repository-metadata 
site) a bit anemic, and IMHO missing the point: 
https://maven.apache.org/ref/3.9.4/maven-repository-metadata/index.html
   
   Especially when I put it next to this page:
   https://maven.apache.org/repositories/metadata.html
   
   Former page, that is about maven-repository-metadata module (that contains 
ONLY the modello generated model classes) talks about "local" and "remote" 
metadata, that is totally irrelevant, and none of those things happens in given 
module. The "metadata file names" are irrelevant (are defined by layout), and 
page https://maven.apache.org/repositories/metadata.html IMHO describes much 
better all of it (from remote repo aspect, it does not mention "locally cached" 
metadata either).
   
   So, I'd propose to modify page even more, and just keep this:
   ```
   # Maven Repository Metadata Model
   
   This is strictly the model for Maven Repository Metadata, so really just 
plain objects.
   
   The following are generated from this model:
   
   * [Java 
sources](https://maven.apache.org/ref/3.9.4/maven-repository-metadata/apidocs/index.html)
 with Reader and Writers for the Xpp3 XML parser, to read and write 
maven-metadata(-*).xml files,
   * a [Descriptor 
Reference](https://maven.apache.org/ref/3.9.4/maven-repository-metadata/repository-metadata.html).
   ```


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [maven] cstamas commented on pull request #1224: [MNG-7870] Undeprecate G level metadata

2023-09-06 Thread via GitHub


cstamas commented on PR #1224:
URL: https://github.com/apache/maven/pull/1224#issuecomment-1707855200

   My point is, that the related code change simply made G level metadata work 
the "same way" as GA and GAV level metadata worked: user needs not to manage 
it, it all happens transparently from user POV, is done by resolver "behind the 
curtains", without user interaction.


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [maven] cstamas commented on pull request #1224: [MNG-7870] Undeprecate G level metadata

2023-09-06 Thread via GitHub


cstamas commented on PR #1224:
URL: https://github.com/apache/maven/pull/1224#issuecomment-1707840631

   Yes, it was done as part of MNG-7055:
   * https://github.com/apache/maven/pull/555 (master)
   * https://github.com/apache/maven/pull/691 (port to maven-3.9.x)
   
   


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org