You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Michael Osipov <mi...@apache.org> on 2022/11/15 20:58:08 UTC
Clarification on httpcomponents-website/blob/master/src/site/resources/.htaccess
Oleg,
can you explain why previous versions of the autogenerated website point
to the newest one? Consider someone is consuming the Javadoc from his
IDE. I guess the user will be redirected in the IDE and will see *not*
the Javadoc for the version he has configured, no?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Clarification on httpcomponents-website/blob/master/src/site/resources/.htaccess
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sat, 2022-11-19 at 15:23 +0100, Michael Osipov wrote:
> Am 2022-11-15 um 22:32 schrieb Oleg Kalnichevski:
> > On Tue, 2022-11-15 at 21:58 +0100, Michael Osipov wrote:
> > > Oleg,
> > >
> > > can you explain why previous versions of the autogenerated
> > > website
> > > point
> > > to the newest one? Consider someone is consuming the Javadoc from
> > > his
> > > IDE. I guess the user will be redirected in the IDE and will see
> > > *not*
> > > the Javadoc for the version he has configured, no?
> > >
> > > Michael
> >
> > We had a discussion on whether or not we should support 5.1 once
> > 5.2
> > goes GA and the outcome was we should not. Please correct me if I
> > am
> > wrong.
>
> I don't exactly remember that discussion, need to check archives.
>
> > If you know how to redirect web traffic to the supported version of
> > the
> > web site while still serving old 5.1 javadocs please do make
> > necessary
> > changes to the web site. 5.1 javadocs are still in place.
>
> One of the problems is that when javadoc(1) retrieves the JAvadoc
> metadata it does not get the one the client has requested. Basically
> changing history. I need to investigate, but we should not change
> history, the frontpage of a superseded released should just say, not
> supported anymore.
I reverted HC 5.1 redirects.
Oleg
>
> > Besides, IDEs are likely to pull javadocs from the Maven central,
> > and
> > not out web site.
>
> This is true.
>
>
> I will try to take a look how to tackle this problem. Same with
> Maven:
> https://maven.apache.org/ref/. For every single version the content
> is
> neither touched nor redirected, but 'current' is updated.
>
> M
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Clarification on httpcomponents-website/blob/master/src/site/resources/.htaccess
Posted by Michael Osipov <mi...@apache.org>.
Am 2022-11-15 um 22:32 schrieb Oleg Kalnichevski:
> On Tue, 2022-11-15 at 21:58 +0100, Michael Osipov wrote:
>> Oleg,
>>
>> can you explain why previous versions of the autogenerated website
>> point
>> to the newest one? Consider someone is consuming the Javadoc from his
>> IDE. I guess the user will be redirected in the IDE and will see
>> *not*
>> the Javadoc for the version he has configured, no?
>>
>> Michael
>
> We had a discussion on whether or not we should support 5.1 once 5.2
> goes GA and the outcome was we should not. Please correct me if I am
> wrong.
I don't exactly remember that discussion, need to check archives.
> If you know how to redirect web traffic to the supported version of the
> web site while still serving old 5.1 javadocs please do make necessary
> changes to the web site. 5.1 javadocs are still in place.
One of the problems is that when javadoc(1) retrieves the JAvadoc
metadata it does not get the one the client has requested. Basically
changing history. I need to investigate, but we should not change
history, the frontpage of a superseded released should just say, not
supported anymore.
> Besides, IDEs are likely to pull javadocs from the Maven central, and
> not out web site.
This is true.
I will try to take a look how to tackle this problem. Same with Maven:
https://maven.apache.org/ref/. For every single version the content is
neither touched nor redirected, but 'current' is updated.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org
Re: Clarification on httpcomponents-website/blob/master/src/site/resources/.htaccess
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Tue, 2022-11-15 at 21:58 +0100, Michael Osipov wrote:
> Oleg,
>
> can you explain why previous versions of the autogenerated website
> point
> to the newest one? Consider someone is consuming the Javadoc from his
> IDE. I guess the user will be redirected in the IDE and will see
> *not*
> the Javadoc for the version he has configured, no?
>
> Michael
We had a discussion on whether or not we should support 5.1 once 5.2
goes GA and the outcome was we should not. Please correct me if I am
wrong.
If you know how to redirect web traffic to the supported version of the
web site while still serving old 5.1 javadocs please do make necessary
changes to the web site. 5.1 javadocs are still in place.
Besides, IDEs are likely to pull javadocs from the Maven central, and
not out web site.
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org