cstamas commented on issue #1440:
URL: https://github.com/apache/maven-site/issues/1440#issuecomment-3431797681
Another thing to tinker about: _sometimes_ the URL contains info usable for
both! Think about Sonatype Central Portal snapshots for example. Or think about
this in-house POM snippet:
```xml
<distributionManagement>
<repository>
<id>corp1-releases</id>
<name>Corporate Repository</name>
<url>https://repo.company.com/repositories/releases</url>
</repository>
<snapshotRepository>
<id>corp1-snapshots</id>
<name>Corporate Snapshots</name>
<url>https://repo.company.com/repositories/snapshots</url>
</snapshotRepository>
...
</distributionManagement>
```
With MRMs this is perfectly valid setup (ie this stanza could be in company
wide parent POM; combined with deployAtEnd is totally good).
But sometimes, the URL will contain "service URL" (ie like ASF points to
Staging API endpoint), that does not tell anything to consumer... but does not
cover the "reality" either.
--
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]
