Hey all,
Having worked with Eclipse and CVS for years, I am a
little confused as to how to add my existing project
on my windwos box into my subversion repository on our
linux box through Subclipse. Can this be done? With
CVS, I simply set up the repository and the CVSROOT
path, then right-clicked, team->share-> used the
repository I set up, and commit the project.
With Subversion, I have already used the svnadmin tool
to create a project, /client below our
/usr/local/svnroot directory. When I make the
repository connection via SVN and Subclipse, it's
fine. I use the https://oursite.com/svnroot/client for
the URL and for the root I just use the
https://oursite.com. This seems to work. I also
created the trunk and other directories, imported
them, etc. In Eclipse, under the SVN Repository view,
I can expand it and see the trunk and two other
folders just fine.
Now here inlies the confusion. I want to add my
"previously stored CVS project" into the SVN
repository at the /client location. I right-click and
select team->share-> and use the SVN repos I set up.
The next step asks me for a module name? Huh? From
what I gather, the repository with the /client at the
end IS the module name. So when I add a module name
(say client), then log in via ssh, I see in my
/svnroot/client/client and below that all the same
dirs I see in /svnroot/client. It's as if it creates
the repository location AGAIN below the one I already
created manually to use. But if I just use /svnroot
and don't add the /client to the URL part, it wont let
me attach!
So two questions I guess... one, what am I doing wrong
above? The other, usually in CVS I have several
projects each with their own location (project name)
in CVS. How do I mimic this functionality in
Subversion through Subclipse? Essentially I want to
have a top dir of my company name, and below that
several projects. I then may want to store some other
projects outside the company top dir. Is this normal,
or is the norm for every single project to have its
own complete repository URL? I also ask this because I
have been thinking of breaking out the desktop portion
of our product into its own "module" away from the
server side module, to better separate and deal with
builds and unit tests and such. We'll have different
developers working on the desktop part and the server
part, and we'll also want a "shared" module that both
the desktop and server modules link to, or somehow
have access to. Ideally, the shared module is built
and jarred before the desktop or server modules can be
built.
Thanks for any help.
____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs
Received on Wed Aug 17 07:14:20 2005