You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cayenne.apache.org by Michael Gentry <bl...@gmail.com> on 2026/07/03 11:50:19 UTC
cayenne-website
Hi,
I'm having an issue with the download page (at a minimum).
When I navigate to http://localhost:3000/download/ the top of the page is
the 5.0-M2 release as expected, but the release notes link goes to
https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which is
incorrect. It should go to
https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt.
Think link works for M1.
I think it was the "mvn release:prepare" or "mvn release:perform" step that
asked for the version and I entered 5.0-M2, but it applied "cayenne-parent-"
to it as well.
Also, the "Cayenne 5.0-M2 source code distribution" link is semi-broken. To
be fair, it is the same for other releases, too. The M1 link points to
https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
for example. Or is that the expectation?
I'm not sure how the download page is generated. Anyone have ideas on how
to fix this?
Thanks,
mrg
PS. I have a few appointments today. Won't be back until this afternoon.
Re: cayenne-website
Posted by Andrus Adamchik <aa...@gmail.com>.
Thanks Mike!
> On Jul 4, 2026, at 10:27 AM, Michael Gentry <bl...@gmail.com> wrote:
>
> To answer my own question about publishing, I found the "mvn publish"
> command. Web site is now updated.
>
> On Fri, Jul 3, 2026 at 2:21 PM Michael Gentry <bl...@gmail.com> wrote:
>
>> The new tag worked. I committed my changes. Let me know if I need to
>> change anything.
>>
>> Does the site auto-publish or do I need to do something?
>>
>> Do I need to email the Apache announce list?
>>
>> I'll try to do the Twitter and BSKY messages now.
>>
>>
>> On Fri, Jul 3, 2026 at 10:07 AM Andrus Adamchik <aa...@gmail.com>
>> wrote:
>>
>>>
>>>
>>>> On Jul 3, 2026, at 7:50 AM, Michael Gentry <bl...@gmail.com> wrote:
>>>>
>>>> When I navigate to http://localhost:3000/download/ the top of the page
>>> is
>>>> the 5.0-M2 release as expected, but the release notes link goes to
>>>> https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which
>>> is
>>>> incorrect. It should go to
>>>>
>>> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt
>>> .
>>>> Think link works for M1.
>>>
>>> Yeah, this is related to how the tag was named. Nothing wrong with the
>>> "cayenne-parent-5.0-M2" name per se, but it is not compatible with the site
>>> assembly template. So I just manually pushed a "5.0-M2" tag pointing to the
>>> same commit and the "canonical" link now works.
>>>
>>>
>>>> Also, the "Cayenne 5.0-M2 source code distribution" link is
>>> semi-broken. To
>>>> be fair, it is the same for other releases, too. The M1 link points to
>>>>
>>> https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
>>>> for example. Or is that the expectation?
>>>
>>> Not sure about this one.
>>>
>>> Andrus
>>>
>>>
Re: cayenne-website
Posted by Michael Gentry <bl...@gmail.com>.
To answer my own question about publishing, I found the "mvn publish"
command. Web site is now updated.
On Fri, Jul 3, 2026 at 2:21 PM Michael Gentry <bl...@gmail.com> wrote:
> The new tag worked. I committed my changes. Let me know if I need to
> change anything.
>
> Does the site auto-publish or do I need to do something?
>
> Do I need to email the Apache announce list?
>
> I'll try to do the Twitter and BSKY messages now.
>
>
> On Fri, Jul 3, 2026 at 10:07 AM Andrus Adamchik <aa...@gmail.com>
> wrote:
>
>>
>>
>> > On Jul 3, 2026, at 7:50 AM, Michael Gentry <bl...@gmail.com> wrote:
>> >
>> > When I navigate to http://localhost:3000/download/ the top of the page
>> is
>> > the 5.0-M2 release as expected, but the release notes link goes to
>> > https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which
>> is
>> > incorrect. It should go to
>> >
>> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt
>> .
>> > Think link works for M1.
>>
>> Yeah, this is related to how the tag was named. Nothing wrong with the
>> "cayenne-parent-5.0-M2" name per se, but it is not compatible with the site
>> assembly template. So I just manually pushed a "5.0-M2" tag pointing to the
>> same commit and the "canonical" link now works.
>>
>>
>> > Also, the "Cayenne 5.0-M2 source code distribution" link is
>> semi-broken. To
>> > be fair, it is the same for other releases, too. The M1 link points to
>> >
>> https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
>> > for example. Or is that the expectation?
>>
>> Not sure about this one.
>>
>> Andrus
>>
>>
Re: cayenne-website
Posted by Michael Gentry <bl...@gmail.com>.
The new tag worked. I committed my changes. Let me know if I need to change
anything.
Does the site auto-publish or do I need to do something?
Do I need to email the Apache announce list?
I'll try to do the Twitter and BSKY messages now.
On Fri, Jul 3, 2026 at 10:07 AM Andrus Adamchik <aa...@gmail.com> wrote:
>
>
> > On Jul 3, 2026, at 7:50 AM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > When I navigate to http://localhost:3000/download/ the top of the page
> is
> > the 5.0-M2 release as expected, but the release notes link goes to
> > https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which is
> > incorrect. It should go to
> >
> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt
> .
> > Think link works for M1.
>
> Yeah, this is related to how the tag was named. Nothing wrong with the
> "cayenne-parent-5.0-M2" name per se, but it is not compatible with the site
> assembly template. So I just manually pushed a "5.0-M2" tag pointing to the
> same commit and the "canonical" link now works.
>
>
> > Also, the "Cayenne 5.0-M2 source code distribution" link is semi-broken.
> To
> > be fair, it is the same for other releases, too. The M1 link points to
> >
> https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
> > for example. Or is that the expectation?
>
> Not sure about this one.
>
> Andrus
>
>
Re: cayenne-website
Posted by Nikita Timofeev <nt...@objectstyle.com>.
I believe download links were made per apache guidelines, so this download
page should be fine.
But that was created a long time ago, so we should check if we are still
following current recommendations.
On Fri, Jul 3, 2026 at 6:07 PM Andrus Adamchik <aa...@gmail.com> wrote:
>
>
> > On Jul 3, 2026, at 7:50 AM, Michael Gentry <bl...@gmail.com> wrote:
> >
> > When I navigate to http://localhost:3000/download/ the top of the page
> is
> > the 5.0-M2 release as expected, but the release notes link goes to
> > https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which is
> > incorrect. It should go to
> >
> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt
> .
> > Think link works for M1.
>
> Yeah, this is related to how the tag was named. Nothing wrong with the
> "cayenne-parent-5.0-M2" name per se, but it is not compatible with the site
> assembly template. So I just manually pushed a "5.0-M2" tag pointing to the
> same commit and the "canonical" link now works.
>
>
> > Also, the "Cayenne 5.0-M2 source code distribution" link is semi-broken.
> To
> > be fair, it is the same for other releases, too. The M1 link points to
> >
> https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
> > for example. Or is that the expectation?
>
> Not sure about this one.
>
> Andrus
>
>
--
Best regards,
Nikita Timofeev
Re: cayenne-website
Posted by Andrus Adamchik <aa...@gmail.com>.
> On Jul 3, 2026, at 7:50 AM, Michael Gentry <bl...@gmail.com> wrote:
>
> When I navigate to http://localhost:3000/download/ the top of the page is
> the 5.0-M2 release as expected, but the release notes link goes to
> https://github.com/apache/cayenne/blob/5.0-M2/RELEASE-NOTES.txt which is
> incorrect. It should go to
> https://github.com/apache/cayenne/blob/cayenne-parent-5.0-M2/RELEASE-NOTES.txt.
> Think link works for M1.
Yeah, this is related to how the tag was named. Nothing wrong with the "cayenne-parent-5.0-M2" name per se, but it is not compatible with the site assembly template. So I just manually pushed a "5.0-M2" tag pointing to the same commit and the "canonical" link now works.
> Also, the "Cayenne 5.0-M2 source code distribution" link is semi-broken. To
> be fair, it is the same for other releases, too. The M1 link points to
> https://www.apache.org/dyn/closer.cgi/cayenne/5.0-M1/cayenne-5.0-M1-src.tar.gz
> for example. Or is that the expectation?
Not sure about this one.
Andrus