Issue 388 - chaos in CVS repository of api/www/common/ref/
Summary: chaos in CVS repository of api/www/common/ref/
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: http://api.openoffice.org/common/ref/...
Keywords:
: 541 543 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-02-07 09:59 UTC by ooo
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description ooo 2001-02-07 09:59:52 UTC 
Due to a restructuring of the API refererence manual we need to clean the
complete subdirctory api/www/common/ref/ in the repository. There are some files
like common/ref/com/sun/star/text/TextField.html which I can neither remove nor
commit. I think it is, because there once as a module doc-file testfield.html
and now there is a service doc-file TextField.html and I had to use Windows
(case insensitive).

ATTN: there are dozes of such files, it is no help just do fix this single file.
I'd rather start over with a completely clean subdirectory (I cannot change the
name, then links from many documents will be dead). These files are all output
anyway and do not need any version control. The only reason to use CVS is, to
get them on the website at all.

Thanks.
Comment 1 Unknown 2001-02-08 22:42:24 UTC 
Reassigning to kat for investigation and solution proposal.  Kat, please work 
with NPM if necessary to develop a solution, and coordainte with Michael so you 
have a full understanding of work necessary.  Propose your solution to Michael 
(and perhaps run it by npm if you think that would be good) before 
implimentation.

Michael, is there a deadline for this?
Comment 2 Unknown 2001-02-09 00:32:17 UTC 
accepting issue for investigation
Comment 3 ooo 2001-02-09 09:25:31 UTC 
not really a deadline, but ASAP. As long as this is not fixed, the API online
reference manual is partially broken.
Comment 4 Unknown 2001-02-13 20:53:31 UTC 
I have contacted an engineer regarding this issue and am waiting for feedback.

Kathy
Comment 5 Unknown 2001-02-21 19:34:39 UTC 
Niels,

Do you have any feedback on this issue?
Comment 6 Unknown 2001-03-13 06:33:35 UTC 
Michael,

I am sorry it has taken so long to reply, I have been waiting for some feedback.
The file you mentioned is not included in my checkout, but I can see it in the
repository. 
This directory can be removed entirely but there would be a downtime until the
files could be replaced. I am stil trying to see if there is any other feedback
on the best way to accomplish your goal.
Comment 7 Unknown 2001-03-27 02:20:51 UTC 
Thom,

Do you have any comments on this issue?

Kat
Comment 8 ooo 2001-03-27 07:37:42 UTC 
Please, simply delete the CVS files below apiwww/ref. Due to this bug, this tree
is already down for weeks. I don't care about a day where there is nothing at
all.

Thanks
Comment 9 ooo 2001-03-27 07:39:56 UTC 
I meant apiwww/common/ref, of course. apiwww is the alias for api/www.
Comment 10 ooo 2001-03-27 07:41:07 UTC 
*** Issue 541 has been marked as a duplicate of this issue. ***
Comment 11 ooo 2001-03-27 07:41:38 UTC 
*** Issue 543 has been marked as a duplicate of this issue. ***
Comment 12 Unknown 2001-03-27 17:35:58 UTC 
The subdirectory ref has been cleaned out. The original files have been saved to
a .tar file in case they are needed.

I appologize for the delay on this issue.
Comment 13 michael.bemmer 2003-03-24 08:31:08 UTC 
As agreed by Louis I will close these resolved fixed kat (support)-owned issues
now. If you have trouble with that, please re-open the issue.
Comment 14 michael.bemmer 2003-03-24 08:32:52 UTC 
As agreed by Louis I will close these resolved fixed kat (support)-owned issues
now. If you have trouble with that, please re-open the issue.