Le 20/08/2018 à 21:36, Shawn McKinney a écrit : > >> On Aug 19, 2018, at 4:29 PM, Emmanuel Lécharny <[email protected]> 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
pEpkey.asc
Description: application/pgp-keys
