Re: [Cxtable-devel] Where are we at, once CVS is up?

[Borne Goodman-M. <bm...@eg...>]

The main point to getting the code base into CVS is that when I want to
go and make some changes to thing, I don't need to go sending the files
I changed back to everyone involved via some email.  Each person working
on the project can make whatever changes they want, and then check them
into CVS, and the next time anyone updates to the latest CVS tree they
will magically get the new code.  This is a million times better than
the old way.

The first step is indeed to get things to a point where they compile,
and all the files are in all the directories we want them in.  You
should feel free to do anything you like to the code in CVS (as it is
yours after all), and if I happen to make a modification that conflicts
with yours, then I will be notified (by CVS) and will need to resolve
the conflict before I can check in the code.

Read about CVS.... it is the heart of any open source development
project.  To check in the code in your tree, run >cvs checkin.  To
update your tree with what is on the server, run >cvs update.  Those are
the 2 biggies.  If you want to add a new file to cvs, run >cvs add
<filename>.  If you want to remove one, run >cvs remove <filename>. 
Adds and removes do not take effect on the server until the next time
you run >cvs checkin.

You can cross import java classes like you explain in your question. 
The compiler is smart enough to resolve the dependencies.

--bjgm

On Thu, 2001-12-13 at 11:58, Williams, David wrote:
> I guess I am wondering what things you were hoping to do once CVS was updated... 
> 
> I imagine the first step will be to add the "package cxtable.xxxx;" lines, and add the imports in the appropriate places, so that it will build again ;-)
> 
> Would you be able to do some of that, or would it be best if I went ahead and did that?
> 
> What are the basic commands for checking in?  (there goes my laziness again...I did not RTFM on CVS...so maybe I could start there...but it is just EASIER to ask people..)
> 
> Let me give you a concrete example of something, and you tell me if it would cause a problem..
> 
> In package corecomm, there are places where it references an xPanel (called reporter).  xPanel is in package gui. 
> 
> CAN (let's say its xRegistry...  when it adds a connection) "import cxtable.gui.xPanel;" and be compiled still when certain "GUI" elements use corecomm stuff?  Do you run into a chicken and egg scenario?
> 
> ((I have grossly ignored learning about packages..but I agree that it is the best way to approach developing a project like this in the future...))
> 
> ~Dave
> 
> 
> 
> David Scott Williams
> Computer Associates
> Marketing Representative-Sales Call Center
> One Computer Associates Plaza 
> Islandia, New York  11749
> tel: +1 800-243-9462 ext. 73431
> tel: +1 631-342-3431 (Direct)
> fax: +1 631-342-5734
> wi...@ca...
> 
> 
> _______________________________________________
> Cxtable-devel mailing list
> Cxt...@li...
> https://lists.sourceforge.net/lists/listinfo/cxtable-devel
>