You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Tony Stevenson (JIRA)" <ji...@apache.org> on 2015/01/02 10:31:13 UTC
[jira] [Closed] (INFRA-8901) MetaModel site: Cannot publish to
production
[ https://issues.apache.org/jira/browse/INFRA-8901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tony Stevenson closed INFRA-8901.
---------------------------------
Resolution: Fixed
Assignee: Tony Stevenson
Closing as I can see /apidocs/current redirects to /apidocs/3.4.1/
> MetaModel site: Cannot publish to production
> --------------------------------------------
>
> Key: INFRA-8901
> URL: https://issues.apache.org/jira/browse/INFRA-8901
> Project: Infrastructure
> Issue Type: Bug
> Components: CMS
> Reporter: Kasper Sørensen
> Assignee: Tony Stevenson
>
> Hi INFRA,
> For the MetaModel site (http://metamodel.apache.org) we've been adding some API documentation files to our site files and yesterday I was also trying to make a kind of symlink that would link "/apidocs/latest" to "/apidocs/3.4.1" (our currently latest version). That eventually didn't work out, so now I retracted to using a "latest" directory with a html file that redirects the user instead.
> The problem is that now when I click "publish" in the CMS I get this error:
> {code}
> svnmucc: E125002: 'production/metamodel/content/apidocs/latest' (from 'staging/metamodel/trunk/content/apidocs/latest:933203') already exists
> {code}
> Not sure exactly why it happens, but I imagine it has to do with the symlink I initially created and which is now instead a real folder.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)