| CVS Newbie Question: re-use information from different projects & CVS. [message #154697] |
Fri, 16 April 2004 14:28  |
Eclipse User |
|
|
|
Originally posted by: rene.c3ismc.com
Hi All,
I have a newbie question on how how to re-use information from different
projects. When I work with Eclipse I typically work on single projects
that are stored in the CVS repository. This creates different modules in
the repository which are not aware of each other. Now there will be
overlap in the code (utility class and/or reusable components) with the
same package names in each project.
As I am "new" to CVS and would like to know if there is a way in which I
can do a "commit" to a single underlying module(?) (entire java-codebase)
from each of the projects and have each of the projects updated from this
single underlying codebase. The intention is to have the changes from one
project made 'available' to the other projects. Could cause rework etc but
that is OK.
The simple solution to this would be to have only one project but that
prevents me from using all the cool project/workset related features of
Eclipse's Worksets etc. I'll do it this way if I have to but I thought to
see if there is a better way first.
I can't imagine this is something not already solved by others -- I simply
don't see the solution.
Clearly I am willing to adopt a new workflow for managing my code with
Eclipse and CVS so ...
I would really appreciate some to enlighten me on this topice and
give me the 'oooh that's how' - experience :-)
Thanks in advance,
Raynier
Seattle(WA) USA
|
|
|
| Re: CVS Newbie Question: re-use information from different projects & CVS. [message #154968 is a reply to message #154697] |
Mon, 19 April 2004 15:52  |
| Eclipse User |
|
|
|
Originally posted by: eclipse.rizzoweb.com
Raynier wrote:
> Hi All,
>
> I have a newbie question on how how to re-use information from different
> projects. When I work with Eclipse I typically work on single projects
> that are stored in the CVS repository. This creates different modules in
> the repository which are not aware of each other. Now there will be
> overlap in the code (utility class and/or reusable components) with the
> same package names in each project.
What I've always done is to have a CVS module (and corresponding IDE
Project) named "Common" that holds all the stuff that is shared by more
than one application or logical project. For example, common library
JARs, source code that is used in many places, etc.
The other projects (applications, for example) depend on this Common
project, and I only have to worry about keeping one project/module up to
date when I change something in there.
HTH,
Eric
--
There are no rules here - we're trying to accomplish something.
- Thomas Edison
|
|
|
Powered by
FUDForum. Page generated in 0.04605 seconds
Home