You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Emmanuel Lécharny <el...@gmail.com> on 2018/08/19 21:29:31 UTC

ApacheDS 2.0.0.AM25 ad site update

Hi guys,

I have successfully pushed the release, and updated the web site.
There is one thing that I can't get working, and I don't understand why:
If you try to get to the 2.0.0/AM25 javadocs, you get the previous
version (2.0.0-M24). Strange enouh, accessing the xref part gets you to
the right version.

What is weird is that apidocs and xref are processed the exact same way
under the curtain:we use the gen-docs/.htaccess directive to pont to the
latest version:


RewriteEngine on

RewriteBase /apacheds/gen-docs

RewriteRule ^latest$ 2.0.0.AM25/
RewriteRule ^latest/(.*)$ 2.0.0.AM25/$1


The link in templates/apacheds/page.html are the same :

...
<li><a href="{{base}}apacheds/gen-docs/latest/apidocs">JavaDocs</a></li>
<li><a href="{{base}}apacheds/gen-docs/latest/xref">Cross-Reference</a></li>
...

which will be translated to :

http://directory.apache.org/apacheds/gen-docs/latest/apidocs
and
http://directory.apache.org/apacheds/gen-docs/latest/xref


Those two URL are transformed (suposely) to :

http://directory.apache.org/apacheds/gen-docs/2.0.0.AM25/apidocs
and
http://directory.apache.org/apacheds/gen-docs/2.0.0.AM25/xref


Tose two links point to the correct location, and you get the expected
result.

What does not work is that the apidocs URL does not give you access to
AM25 version, at this point... I will wait until tomorrow to see if it's
not simply a delayed glitch on the server, but I very much doubt it...


Otherwise, if any of you have an idea...

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org


Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Shawn McKinney <sm...@apache.org>.
> On Aug 21, 2018, at 12:38 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> Yes, it's critially important to *always* do a svn update on the site
> content before publishing the site, and to check that the extpaths
> content refers to the latest versions of all the project.

Agreed.

> 
> On Aug 21, 2018, at 12:38 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> I strongly suspect I have FU when I updated the site last week-end for
> ApacheDS 2.0.0.AM26, and that a bad merge I have done might have deleted
> the fortress 2.0.1 line.

No worries Emmanuel.  You’ve been a big help over the years as my mentor on this project.  Been patient with all of my f/u’s, and, no big deal anyway.  Simply re-added to SVN.

> 
> On Aug 21, 2018, at 12:38 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> I wish we have an extpaths.txt file anyhwere in the tree, so that we can
> exclude directories at the closest possible position, making it almost
> impossible to have a side effect, sadly this file has to be at the root
> of the web site, ie in content/ ...

My thoughts.  An extpaths per subproject…

— Arkanshawn  

Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Emmanuel Lécharny <el...@gmail.com>.

Le 21/08/2018 à 00:45, Shawn McKinney a écrit :
> 
>> On Aug 20, 2018, at 5:11 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>
>> This is because the extpaths.txt file does not contain a reference to
>> fortress 2.0.1:
>>
>> ...
>>
>> Don't worry, we have all be bitten by this, more than once... (no later
>> than this week-end for me...)
> 
> Hi Emmanuel,
> 
> as it turns out I have already been bitten by this and so did update that file on 20 Jul, so somehow that change was reverted?
> 
> Actually this isn’t the first time this (javadoc gone missing) has happened so there is something amiss in our process.  
> 
> Anyway, I will reinject the latest javadocs and we can keep an eye on this.


Yes, it's critially important to *always* do a svn update on the site
content before publishing the site, and to check that the extpaths
content refers to the latest versions of all the project.

I strongly suspect I have FU when I updated the site last week-end for
ApacheDS 2.0.0.AM26, and that a bad merge I have done might have deleted
the fortress 2.0.1 line.

I wish we have an extpaths.txt file anyhwere in the tree, so that we can
exclude directories at the closest possible position, making it almost
impossible to have a side effect, sadly this file has to be at the root
of the web site, ie in content/ ...

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org


Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Shawn McKinney <sm...@apache.org>.
> On Aug 20, 2018, at 5:11 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> This is because the extpaths.txt file does not contain a reference to
> fortress 2.0.1:
> 
> ...
> 
> Don't worry, we have all be bitten by this, more than once... (no later
> than this week-end for me...)

Hi Emmanuel,

as it turns out I have already been bitten by this and so did update that file on 20 Jul, so somehow that change was reverted?

Actually this isn’t the first time this (javadoc gone missing) has happened so there is something amiss in our process.  

Anyway, I will reinject the latest javadocs and we can keep an eye on this.

Thanks,
— Shawn

p.s. here’s SVN history for when I last committed...

r1032792 | smckinney | 2018-07-20 09:05:04 -0500 (Fri, 20 Jul 2018) | 2 lines

2.0.1


Index: extpaths.txt
===================================================================
--- extpaths.txt	(revision 1032791)
+++ extpaths.txt	(revision 1032792)
@@ -4,6 +4,10 @@
 #scimple/gen-docs/1.0.0
 
 # Fortress
+fortress/gen-docs/2.0.1
+fortress/gen-docs/2.0.0
+fortress/gen-docs/2.0.0-RC2
+fortress/gen-docs/2.0.0-RC1
 fortress/gen-docs/1.0.1
 fortress/gen-docs/1.0.0
 fortress/gen-docs/1.0-RC42


Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Emmanuel Lécharny <el...@gmail.com>.

Le 20/08/2018 à 21:36, Shawn McKinney a écrit :
> 
>> On Aug 19, 2018, at 4:29 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>
>> I have successfully pushed the release, and updated the web site.
>> There is one thing that I can't get working, and I don't understand why:
>> If you try to get to the 2.0.0/AM25 javadocs, you get the previous
>> version (2.0.0-M24). Strange enouh, accessing the xref part gets you to
>> the right version.
> 
> I’m getting not found on fortress latest javadocs:
> 
> https://directory.apache.org/fortress/gen-docs/latest/apidocs/, pretty sure it was good working after the latest release, so not sure what’s up with that.  
> 
> Will take a closer look later and report back here what I find…


This is because the extpaths.txt file does not contain a reference to
fortress 2.0.1:

...
# Fortress
fortress/gen-docs/2.0.0
fortress/gen-docs/2.0.0-RC2
fortress/gen-docs/2.0.0-RC1
fortress/gen-docs/1.0.1
fortress/gen-docs/1.0.0
fortress/gen-docs/1.0-RC42
fortress/gen-docs/1.0-RC40
...

It should be :

# Fortress
fortress/gen-docs/2.0.1
fortress/gen-docs/2.0.0
fortress/gen-docs/2.0.0-RC2
fortress/gen-docs/2.0.0-RC1
fortress/gen-docs/1.0.1
fortress/gen-docs/1.0.0
fortress/gen-docs/1.0-RC42
fortress/gen-docs/1.0-RC40


I added the line, but sadly, everything related to Fortress 2.0.1
javadoc has been wiped out from production, so you need to inject it
back (or restore the revision where you injected it).


Keep in mind that this extpaths.txt file is *critical* : it tells the
site publication process which directory should *NOT* be deleted from
production. And teh reason we push javadocs to production and not to
staging is because it would take way too long for the CMS to public it,
this is why we bypass the staging repo when it comes to push javadoc.

Don't worry, we have all be bitten by this, more than once... (no later
than this week-end for me...)

-- 
Emmanuel Lecharny

Symas.com
directory.apache.org


Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Shawn McKinney <sm...@apache.org>.
> On Aug 19, 2018, at 4:29 PM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> I have successfully pushed the release, and updated the web site.
> There is one thing that I can't get working, and I don't understand why:
> If you try to get to the 2.0.0/AM25 javadocs, you get the previous
> version (2.0.0-M24). Strange enouh, accessing the xref part gets you to
> the right version.

I’m getting not found on fortress latest javadocs:

https://directory.apache.org/fortress/gen-docs/latest/apidocs/, pretty sure it was good working after the latest release, so not sure what’s up with that.  

Will take a closer look later and report back here what I find…

—Arkanshawn



Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Emmanuel Lécharny <el...@gmail.com>.

Le 20/08/2018 à 20:58, Stefan Seelmann a écrit :
> On 08/19/2018 11:29 PM, Emmanuel Lécharny wrote:
>> Hi guys,
>>
>> I have successfully pushed the release, and updated the web site.
>> There is one thing that I can't get working, and I don't understand why:
>> If you try to get to the 2.0.0/AM25 javadocs, you get the previous
>> version (2.0.0-M24). Strange enouh, accessing the xref part gets you to
>> the right version.
> 
> Seems to work now, at least for me :)

Yes, #metoo now I just had to wait...


-- 
Emmanuel Lecharny

Symas.com
directory.apache.org


Re: ApacheDS 2.0.0.AM25 ad site update

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 08/19/2018 11:29 PM, Emmanuel Lécharny wrote:
> Hi guys,
> 
> I have successfully pushed the release, and updated the web site.
> There is one thing that I can't get working, and I don't understand why:
> If you try to get to the 2.0.0/AM25 javadocs, you get the previous
> version (2.0.0-M24). Strange enouh, accessing the xref part gets you to
> the right version.

Seems to work now, at least for me :)