[MNG-7870] Undeprecate wrongly deprecated repository metadata

[jira-importer]

Tamas Cservenak opened MNG-7870 and commented

In commit 1af8513 related to MNG-7385 the modello G level metadata was deprecated (by mistake I assume).
Undo this.

---

Issue Links:

• MNG-7385 Improve documentation on repository metadata
  ("is caused by")
• MNG-7055 Using MINSTALL/DEPLOY 3.0.0-M1+ does not write plugin information into maven-metadata.xml

Remote Links:

• GitHub Pull Request #1224
  
• GH PR #1224
  

Backported to: 4.0.0-alpha-8, 3.9.5

[jira-importer]

Hervé Boutemy commented

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...)

[jira-importer]

Hervé Boutemy commented

user-visible issue was introduced in maven-install and deploy-plugin 3.0.0-M1 when they stopped using maven-compat API in MINSTALL-114
so no real regression in Maven itself but more install plugin that did not keep the feature when upgrading to strict Maven 3 API (without compat)

[jira-importer]

Tamas Cservenak commented

maven-3.9.x: 84ee422
master: 1c050ee