db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6007) Migrate Derby website to new Apache website publication machinery
Date Sat, 15 Dec 2012 15:22:14 GMT

     [ https://issues.apache.org/jira/browse/DERBY-6007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Rick Hillegas updated DERBY-6007:

    Attachment: derby-6007-01-aa-prepForDocsCheckin.diff

Attaching derby-6007-01-aa-prepForDocsCheckin.diff. This patch accompanied the checkin of
the published docs to the Derby website subversion repository. The attached patch does not
include the docs. Its contents are discussed below.

It took about six hours to checkin this patch along with the published docs. At the end of
that time, the checkin failed with the following error message:

svn: Commit failed (details follow):
svn: MERGE of '/repos/asf/db/derby/site/trunk': timed out waiting for server (https://svn.apache.org)

However, it appears that the files were actually checked in. I have re-sync'd with the repository
and built the website on my machine. It looks good.

Touches the following files:


M       src/documentation/content/xdocs/manuals/index.xml

Pointed the documentation tab at the checked-in javadoc and docs (for released documentation)
and at the Jenkins build artifacts (for development javadoc and docs).

M       build/site/manuals/index.html

This is the corresponding generated output.


M       src/documentation/conf/cli.xconf

Added a directive to exclude the docs directory from consideration by Forest. This prevents
the website build from failing because of unresolved links.


M       build/site/releases/release-

I'm not sure why this turned up in my submission. I believe that this file turned up just
before my submission when I sync'd with the repository and rebuilt the website. I think this
file has something to do with other website work being done in parallel in order to publish
the 10.8.3 release. The file seems harmless, and the download page looks good to me.

> Migrate Derby website to new Apache website publication machinery
> -----------------------------------------------------------------
>                 Key: DERBY-6007
>                 URL: https://issues.apache.org/jira/browse/DERBY-6007
>             Project: Derby
>          Issue Type: Improvement
>          Components: Web Site
>            Reporter: Rick Hillegas
>         Attachments: derby-6007-01-aa-prepForDocsCheckin.diff
> As of January 2013, the Apache website will no longer be refreshed from the /www/db.apache.org/derby
directory tree on minotaur. Instead, projects will need to put their website content under
subversion control and tell the Infrastructure team where that subversion repository is. Most
of Derby's website is subversion controlled. However, the docs and alpha javadoc directories
are not. We will need to put docs and alpha javadoc under subversion control along with the
rest of the Derby website. Then we will need to file an issue, telling the Infrastructure
team where our content lives. For an example of such an issue, see https://issues.apache.org/jira/browse/INFRA-5215

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message