www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kasper Sørensen (JIRA) <j...@apache.org>
Subject [jira] [Commented] (INFRA-8901) MetaModel site: Cannot publish to production
Date Thu, 18 Dec 2014 15:52:13 GMT

    [ https://issues.apache.org/jira/browse/INFRA-8901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14251832#comment-14251832
] 

Kasper Sørensen commented on INFRA-8901:
----------------------------------------

I tried renaming the 'latest' folder to 'current'. Now when I click publish it says:

svnmucc: E125002: 'production/metamodel/content/apidocs/latest' not found

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

Mime
View raw message