At 11:36 AM 5/13/02 -0500, Joi Ellis wrote: >On Sun, 12 May 2002, Ray Tayek wrote: > > > hi, new to cvs (used to rcs), trying to grok a rational tree structure for > > cvs. seems like packages hang out in com.foo.packageName..... > > but this would scatter/duplicate the stuff from com.foo in many places. > >I tend to have one JBuilder project <-> one Java package <-> one CVS Module. >However, I also tend to separate unit test classes from application classes >to make deployment easier. > >I put reusable utility classes into a utils package, and once I decide I >really want to reuse those classes in other projects, I'll move that class >from its original project over into my Utils project. A physical refactoring, >as it were. It's not uncommon for a Project to have an application package >and a utils package for a time during initial development.
got it. > > > > so perhaps the following is indicated: > > ... > >I have my Utils project create a utils.jar, and that jar goes onto the class >path of any other project which needs it. I never deliberately duplicate >classes between projects/cvs modules, for that way lies madness. ;) yes, that is what i was worried about. > Inside >JBuilder, I typically define a library which points to a >checked-out-and-compiled workspace for the Utils project. That way I don't >have to worry about keeping the jar itself up to date or deal with jar >file handle conflicts. > >I use JBuilder rather than ant, but the tool doesn't matter that much. >Ant is a fine, java-based make replacement but I just haven't needed it for >more than building one or two 3rd party libraries. thanks for the info --- ray tayek http://home.attbi.com/~rtayek/ actively seeking telecommuting work vice chair orange county java users group http://www.ocjug.org/ mailto:[EMAIL PROTECTED] hate spam? http://samspade.org/ssw/ _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
