[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: different projects but same source

From: Rick Genter
Subject: RE: different projects but same source
Date: Tue, 7 Dec 2004 06:19:42 -0800

You can accomplish this with the modules files, but I've found it more
useful to break out the separate code into a separately buildable
library (i.e., promote it to be an independent module in its own right),
and reference that library from the projects that require it.

For example, we have a Utility library that is used by approximately 20
applications. Rather than define 20 modules that all reference the
Utility library, we build a separate Utility.jar (all of our
applications are written in Java), then the build script for the 20
applications simply includes the Utility.jar on the classpath.

Rick Genter
Principal Engineer
Silverlink Communications
(781) 272-3080 x242

This e-mail, including attachments, may include confidential and/or
proprietary information, and may only be used by the person or entity to
which it is addressed.  If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited.  If you have received this e-mail in error, please notify
the sender by replying to this message and delete this e-mail

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Kai Lehmann
Sent: Tuesday, December 07, 2004 9:14 AM
To: address@hidden
Subject: different projects but same source

Hi there,

I have several projects in my CVS. each project has its own main dir
in CVS. Sometimes a project contains a subdir with source code for a
specific library. This source code and library I want to use in other
projects too. I can now copy the whole path with source to the other
project. But I have then two copies of the same which is not a nice
thing to handle with. The other possibility is to refer in the other
project to the first project. but this means a lot of traversing
through the directory structure (several ../../.. and going into the
first project dir). Also not very handy. And it is also no good if I
want to make a release and check out a whole project which refers to
the project with the lib, but this project is not checked out
automatically too.

In short:

the content of dir "project1/subdirs.../libsource" shall also be
checked out when i check out "project2". but it should be checked out
to the dir "project2/dubdirs.../libsource".

So my question: is there a way in CVS for having a dir in a project
which is in real somewhere else within the cvs repository? I tried a
bit with $CVSROOT/modules but didn't get something useful. Maybe I
used it wrong.

Any Idea? Pls mail me too, while answering to this question.

Info-cvs mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]