You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Marshall Schor (JIRA)" <ji...@apache.org> on 2013/03/15 14:26:13 UTC

[jira] [Created] (INFRA-5999) Change UIMA Website PUBSUB to normal pattern

Marshall Schor created INFRA-5999:
-------------------------------------

             Summary: Change UIMA Website PUBSUB to normal pattern
                 Key: INFRA-5999
                 URL: https://issues.apache.org/jira/browse/INFRA-5999
             Project: Infrastructure
          Issue Type: Task
      Security Level: public (Regular issues)
            Reporter: Marshall Schor


I've copied the infra email on this below.  Please undo the special casing for the /docs/d and /docs/dev directories and make the site just like the standard pattern.

Thanks.  

------------------------------  copy of infra email below ------------------

uima.apache.org is special-cased in httpd.conf to use a different
docroot, and the /d URI is aliased to someplace out of that docroot.

Can we nuke the /d and /dev directories which are outside the docroot,
and merge you to the standard pattern as all other 100+ TLPs?

If yes open a jira please (and link to this post please so we know what
out-of-pattern steps to take).

Marshall Schor wrote on Thu, Mar 14, 2013 at 16:13:31 -0400:
> Hi,
>
> The UIMA Website predates the CMS system and is done using Anakia, where we
> update in the /xdocs/ directory, and then run the ant script to build the site
> which produces the html in the /docs/ directory.  We have SVN Pubsub setup, so
> that when we commit changes to the site's /docs/ directory, the website is
> nicely automatically updated, more-or-less instantly.
>
> We have one issue: Changes we commit under /docs/d/ subtree in SVN do not seem
> to get copied to our website.  Other commits to other subdirectories of /docs/
> *do* get published.
>
> Can someone tell us what we need to fix/change to get this to work?

--
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