You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Ian Dickinson (Created) (JIRA)" <ji...@apache.org> on 2011/10/06 13:22:30 UTC
[jira] [Created] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
------------------------------------------------------------------------------------------------------------
Key: INFRA-4008
URL: https://issues.apache.org/jira/browse/INFRA-4008
Project: Infrastructure
Issue Type: Bug
Security Level: public (Regular issues)
Components: CMS
Reporter: Ian Dickinson
Priority: Minor
I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
In INFRA-3987, @danielsh asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Posted by "Ian Dickinson (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ian Dickinson updated INFRA-4008:
---------------------------------
Description:
I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
was:
I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
In INFRA-3987, @danielsh asked that http://paste2.org/p/1691577 be attached to this issue.
> Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
> ------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-4008
> URL: https://issues.apache.org/jira/browse/INFRA-4008
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
> Priority: Minor
>
> I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
> Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
> In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206557#comment-13206557 ]
Joe Schaefer commented on INFRA-4008:
-------------------------------------
Provisional fix applied. Feel free to exercise it in abusive ways so we
can close this issue.
> Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
> ------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-4008
> URL: https://issues.apache.org/jira/browse/INFRA-4008
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
> Priority: Minor
>
> I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
> Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
> In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Posted by "#asfinfra IRC Bot (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13184848#comment-13184848 ]
#asfinfra IRC Bot commented on INFRA-4008:
------------------------------------------
<danielsh> ~danielsh/i/INFRA-4008.patch
> Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
> ------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-4008
> URL: https://issues.apache.org/jira/browse/INFRA-4008
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
> Priority: Minor
>
> I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
> Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
> In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Posted by "Joe Schaefer (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183705#comment-13183705 ]
Joe Schaefer commented on INFRA-4008:
-------------------------------------
That url has expired- perfect.
> Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
> ------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-4008
> URL: https://issues.apache.org/jira/browse/INFRA-4008
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
> Priority: Minor
>
> I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
> Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
> In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Posted by "Joe Schaefer (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Schaefer closed INFRA-4008.
-------------------------------
Resolution: Fixed
Seen enough uses now to close this issue.
> Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
> ------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-4008
> URL: https://issues.apache.org/jira/browse/INFRA-4008
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
> Priority: Minor
>
> I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
> Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
> In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (INFRA-4008) Using Apache CMS, commiting file
deletes to svn does not cause the generated file to be removed from staging
Posted by "#asfinfra IRC Bot (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-4008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183861#comment-13183861 ]
#asfinfra IRC Bot commented on INFRA-4008:
------------------------------------------
<danielsh> I can grep my mail and see if I have a backup somewhere. Do you know offhand what files the patch would have touched?
> Using Apache CMS, commiting file deletes to svn does not cause the generated file to be removed from staging
> ------------------------------------------------------------------------------------------------------------
>
> Key: INFRA-4008
> URL: https://issues.apache.org/jira/browse/INFRA-4008
> Project: Infrastructure
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: CMS
> Reporter: Ian Dickinson
> Priority: Minor
>
> I've been working on our CMS-based site for Apache Jena by checking out the svn trunk, editing and then committing. This works well when making large numbers of changes. However, files that are removed from svn in this way do not have the derived .html files deleted from the staging server. In the end, following advice on this thread (https://issues.apache.org/jira/browse/INFRA-3987), I manually deleted the generated .html files directly from the staging svn.
> Desired outcome: svn rm'ing a .mdtext file and then committing that change should cause the generated .html file to be removed from the staging server.
> In INFRA-3987, danielsh@ asked that http://paste2.org/p/1691577 be attached to this issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira