[
https://issues.apache.org/jira/browse/MNG-7870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762284#comment-17762284
]
Herve Boutemy commented on MNG-7870:
------------------------------------
yes, probably a confusion about setting the data from maven-compat has been
disabled, then for some Maven releases, data was not filled any more
that created some reports (MNG-7375) showing that the missing data was causing
NPEs: at that time, we supposed that the data should just be ignored, and
documentation updated about that expectation => mark deprecated
but later, MNG-7055 introduced a new way to fill the data (in Maven 3.9.0 and
4) using Aether/Maven Resolver APIs instead of maven-compat
then yes, mistake in documentation to be solved and point to MNG-7055 on how
disable maven-compat mechanism has been replaced in MNG-7055 Maven Resolver
(ideally, MNG-7055 should point to the update in maven-compat that stopped
filling the fields = the first Maven release that is broken regarding this
field...)
> Undeprecate wrongly deprecated repository metadata
> --------------------------------------------------
>
> Key: MNG-7870
> URL: https://issues.apache.org/jira/browse/MNG-7870
> Project: Maven
> Issue Type: Task
> Components: Artifacts and Repositories
> Reporter: Tamas Cservenak
> Priority: Major
> Fix For: 4.0.0-alpha-8, 3.9.5
>
>
> In commit
> https://github.com/apache/maven/commit/1af8513fa7512cf25022b249cae0f84062c5085b
> related to MNG-7385 the modello G level metadata was deprecated (by mistake
> I assume).
> Undo this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
