Issue 999 - move forms module to project dba
Summary: move forms module to project dba
Status: CLOSED WONT_FIX
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: _openoffice.org CVS (obsolete) (show other issues)
Version: current
Hardware: All Other OS
: P2 Trivial (vote)
Target Milestone: ---
Assignee: Martin Hollmichel
QA Contact: issues@www
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-06-05 14:51 UTC by Frank Schönheit
Modified: 2003-12-06 14:52 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2001-06-05 14:51:04 UTC
The module forms (currently located in the gsl project) should be moved to the 
dba (database access) project, as the main focus of the module are data aware 
forms.
Comment 1 Martin Hollmichel 2001-06-09 07:17:34 UTC
Moving a cvs modules from one project to another is not that simple:

1. We have to decide wether 
   a: cvs remove and commit the module
   b: copy the archives directly on the filesystem of cvs

2. how to deal with the CVSROOT/modules file
   a: alias point to the new project -> it becomes impossible to access the 
correct module in older workspaces.
   b: a: gets work, if we do a copy a the repository in cvs.
   c: create a "new" form2 module in the new project => no conflicts.


Comment 2 stx123 2001-10-04 14:55:19 UTC
Any further action needed or will forms stay in gsl?
Comment 3 Unknown 2001-11-08 23:14:05 UTC
changing QA contact from bugs@ to issues@
Comment 4 stx123 2001-11-12 21:54:16 UTC
Any further action needed?
Comment 5 Frank Schönheit 2001-12-03 08:42:54 UTC
(sorry for the late answer, was offline for three weeks)

st: yes, we still would like to have forms in dba instead of gsl.
I'd prefer a solution where we have the old as well as the new module 
accessible (so 2a. only seems inappropriate), and where the new 
module is named "forms" (not forms2).
Comment 6 Frank Schönheit 2002-07-15 10:13:28 UTC
Is there any progress here? Or do we want to let this issue silently die?
Comment 7 stx123 2002-08-06 15:25:11 UTC
Martin, could you clarify with Frank, how we would like to proceed?
Thanks
Stefan
Comment 8 Martin Hollmichel 2002-11-07 10:22:54 UTC
having the module available with the same name is not possible, we can
not have two aliases in the CVSROOT/modules file. so if we want to
move the forms module I see no other chance than introducing a new
module name. procedure for that is well known.
Comment 9 Frank Schönheit 2002-11-07 10:55:24 UTC
Martin, so you are recommending 1a? What about 1b? I do not see how 2a
(which is impossible as you say) prevents 1b?
Comment 10 Martin Hollmichel 2002-11-07 14:47:39 UTC
1b can additionally performed to 1a, but surely have to be done before 1a
Comment 11 Frank Schönheit 2002-11-07 14:58:47 UTC
Martin, I understood that both 1b and 1a would solve the problem
independently? Don't they?
Comment 12 michael.bemmer 2003-03-11 18:07:46 UTC
As mentioned on the qa dev list on March 5th I will close all resolved duplicate
issues. Please see this posting for details. First step in IssueZilla is
unfortunately to set them to verified.
Comment 13 michael.bemmer 2003-03-11 18:15:48 UTC
As mentioned on the qa dev list on March 5th I will close all resolved
<wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details.