|
Joe, I view the repositories as a place to control the access and security. So if you had some code you might want to provide other people access to, that might be in one repository and everything else in another. In general though, you probably just want one repository. I would create an empty project in WSAD of the right type, like a Java project or Web project, and then manually import the code. I imagine you would do an Export from VAJ. Then in WSAD do Team -> Share Project and add it to CVS. This will create a module for you. I would avoid any embedded blanks in your project name, as that will then transfer to the module name, and some things like the CVS Ant tasks seem to have trouble with that. This will not get you your history. Other than "simulating" the change process via export and import -- ugh -- I do not know how you could get that over. Finally, you might try contacting Instantiations. http://www.instantiations.com/ They have a VAJ to ClearCase transfer tool and they are also doing stuff to make CVS more VAJ-like, so maybe they also have a CVS transfer tool. Mark PS - I have heard of module lists, but do not know what they are or when you would use them. To: "Java Programming on and around the iSeries / AS400" <java400-l@xxxxxxxxxxxx> cc: bcc: Subject: RE: cvs server with WSAD "Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> Sent by: java400-l-bounces@xxxxxxxxxxxx 04/09/2003 07:06 PM Please respond to Java Programming on and around the iSeries / AS400 <font size=-1></font> > From: Christopher Joseph > > Start here http://www.cvshome.org for relevent information regarding CVS > use although I have NEVER found the information particularly clear. I'm currently doing just that, using CVSNT for my server. I posted a question on IBM's mailing list but didn't get squat - maybe you can help? I'm trying to determine the best way (well, the easiest) to transfer all the information in my VAJ repository to a CVS repository. I have several versions of code, and I'm trying to keep that version information. To date, the best I've been able to theorize (and I haven't even gotten this to work in practice yet) is to set up a repository in CVS for each project, then repetitively check everything out into work folders, export the next version from VAJ into the same work folders, then check that back into CVS. I'm still a complete neophyte, though, because I don't know whether I should use separate repositories, or simply separate modules for each of my VAJ projects. My guess is that it really depends on how closely related the projects are. For example, I have four closely related projects (internal classes, external interface, and a couple of test environments). Those seem to make sense as separate modules within a single repository. I don't know anything about module lists; it looks like I have to manually create them for each module. Are module lists suggested? Required? Not required but highly recommended? This is all great fun! However, I could use tons more information. Any pointers to basic CVS information is fine, especially modules. Joe _______________________________________________ This is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing list To post a message email: JAVA400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/java400-l or email: JAVA400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/java400-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.