>I have slightly reworded the instructions at the end of >http://sling.apache.org/documentation/development/release-management.html >, could you cross-check?
step 4 and 5 are not correct currently. the 'scm-publish:publish-scm' goal directly commits the generated documentation to a path https://svn.apache.org/repos/infra/websites/production/sling/content/component/<plugin-name>-archives/<plugin-name>-LATEST so it's already in svn, and from there it has to be renamed (or moved) to '<plugin-name>-archives/<plugin-name>-<version>' *and* to a folder '<plugin-name>' (which already exists with the old docs, so the old has to be removed first resulting in a replace). the site html should not be svn-imported again, because then it's duplicated in the svn history. the process is described here [1]. i do not know why the publish-scm plugin does not do this steps automatically. the other changes are fine. >Also, now when publishing the site via Apache CMS, >https://cms.apache.org/sling/publish?diff=1 shows lots of removed >files under content/components/htl-maven-plugin (probably the whole >folder), could that be related to what you did? > >http://sling.apache.org/components/ looks ok to me, the >htl-maven-plugin folder is still there after CMS publishing - but this >makes the publish diff unusable. I can have a closer look but maybe >you understand what happened based on your changes? this is strange, not sure why this happens. when starting testing the publication of the documtation I had the problem that new updates to the cms site completely removed the "components" folder. then I detected that in felix-site a file 'content/extpaths.txt' exists which exactly defines this folder as "externall controlled" and keeps it intact on cms publishing. so there is no longer a conflict and i thought all is fine. i have no idea what the effect on this diff view is. it is happing on felix site as well [2]. unfortunately i have no deeper knowledge on this svn-based cms publishing features. stefan [1] http://maven.apache.org/developers/website/deploy-component-reference-documentation.html [2] https://cms.apache.org/felix/publish?diff=1
