What do you propose then for the current release?
Upload to https://downloads.apache.org/maven/shared/ to at least make the 
current Download link in the download page work or upload to 
https://downloads.apache.org/maven/reporting/ (which leaves all links in the 
download page broken) or upload to both paths?

Konrad

> On 16. May 2026, at 11:53, Slawomir Jaranowski <[email protected]> wrote:
> 
> On Sat, 16 May 2026 at 11:28, Konrad Windszus <[email protected] 
> <mailto:[email protected]>> wrote:
>> 
>> Hi,
>> For previous releases the reporting related components have their websites 
>> below https://maven.apache.org/shared, however the download location was not
>> 
>> https://downloads.apache.org/maven/shared/
>> 
>> but
>> 
>> https://downloads.apache.org/maven/reporting/
>> 
>> (Look at https://maven.apache.org/shared/maven-reporting-exec/download.cgi)
>> 
>> This changes in maven-reporting-executor due to this commit 
>> https://github.com/apache/maven-reporting-exec/commit/ecc82dcdc2a5e23370a26620570b36705344dc1b.
>> Was that a deliberate change or just an oversight that shared components 
>> related to reporting use a different download location?
>> 
>> How should we deal with this going forward?
>> 
>> a) Drop 2.0.1 and trigger a new 2.0.2 with a new download page (pointing to 
>> https://downloads.apache.org/maven/reporting/)
>> b) Continue releasing and upload to 
>> https://downloads.apache.org/maven/shared/ (this makes the archive link in 
>> https://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/download.cgi
>>  disfunctional because older releases live in a different path)
> 
> We also have a https://archive.apache.org/dist/maven/reporting/
> so I will put new release in
> https://downloads.apache.org/maven/reporting/ as was for historical
> 
> download page can be fixed in next release
> 
>> c) Something else?
>> 
>> Thanks for your thoughts,
>> Konrad
>> 
>> 
>>> On 16. May 2026, at 11:10, Konrad Windszus <[email protected]> wrote:
>>> 
>>> Hi,
>>> 
>>> The vote has passed with the following result:
>>> 
>>> +1: Sylwester Lachiewicz <[email protected]>, Slawomir Jaranowski 
>>> <[email protected]>, Olivier Lamy <[email protected]>
>>> 
>>> PMC quorum: reached
>>> 
>>> I will promote the source release zip file to the Apache distribution area 
>>> and the artifacts to the central repo.
>>> Thanks for voting,
>>> Konrad
>>> 
>>> 
>>> 
>>>> On 12. May 2026, at 19:06, Konrad Windszus <[email protected]> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> We solved 8 issues:
>>>> https://github.com/apache/maven-reporting-exec/milestone/1?closed=1
>>>> 
>>>> Changes since the last release:
>>>> https://github.com/apache/maven-reporting-exec/compare/maven-reporting-exec-2.0.0...maven-reporting-exec-2.0.1
>>>> 
>>>> Staging repo:
>>>> https://repository.apache.org/content/repositories/maven-2426/
>>>> https://repository.apache.org/content/repositories/maven-2426/org/apache/maven/reporting/maven-reporting-exec/2.0.1/maven-reporting-exec-2.0.1-source-release.zip
>>>> 
>>>> Source release checksum(s):
>>>> maven-reporting-exec-2.0.1-source-release.zip sha512: 
>>>> 9288eb038dfab99b60d45b008a5d8ec875ba51d75a8c4d8531d78fe10b001a1c4ea885a6c9f92c4f0132be0bbb4ad6a2cfccc41056a4ba782b410a577bdef8a3
>>>> 
>>>> Staging site:
>>>> https://maven.apache.org/shared-archives/maven-reporting-exec-LATEST/
>>>> 
>>>> Guide to testing staged releases:
>>>> https://maven.apache.org/guides/development/guide-testing-releases.html
>>>> 
>>>> Vote open for at least 72 hours.
>>>> 
>>>> [ ] +1
>>>> [ ] +0
>>>> [ ] -1
>>>> 
>>>> Thanks in advance for voting,
>>>> Konrad
>>>> 
>>>> 
>>>> 
>>> 
>>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected] 
>> <mailto:[email protected]>
>> For additional commands, e-mail: [email protected] 
>> <mailto:[email protected]>
>> 
> 
> 
> -- 
> Sławomir Jaranowski
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected] 
> <mailto:[email protected]>
> For additional commands, e-mail: [email protected] 
> <mailto:[email protected]>

Reply via email to