RE: [stellation-res] CVS

["Jonathan Gossage" <jgossage@xxxxxxxx>]

Thanks for your response. I had already decided that this was the way to go.
I have used a setup like yours for a while now. And since I wanted to
upgrade to the M2 release of Eclipse it seemed even more like the right
root.

> >-----Original Message-----
> >From: stellation-res-admin@xxxxxxxxxxxxxxx
> >[mailto:stellation-res-admin@xxxxxxxxxxxxxxx]On Behalf Of Jim Wright -
> >IBM Research
> >Sent: October 23, 2002 6:50 PM
> >To: stellation-res@xxxxxxxxxxxxxxx
> >Cc: Stellation
> >Subject: Re: [stellation-res] CVS
> >
> >
> >Jonathan,
> >
> >I'm not sure, but it sounds like the Eclipse workspace metadata may have
> >gotten corrupted.
> >
> >Perhaps this might help:
> >1. create a brand new Eclipse workspace on your machine (see below).
> >2. recreate your extssh repository connection in the new workspace
> >3. do a complete checkout
> >
> >With any luck, you'll now have working CVS access from the new workspace.
> >If you have new changes to check in, you should copy them into the new
> >workspace, of course (because the old workspace is probably
> >damaged somehow).
> >
> >Re: creating Eclipse workspaces.
> >
> >(Just in case you've only used the default Eclipse workspace)
> >
> >I use a lot of Eclipse workspaces for development, on both
> >Windows and Linux.
> >For Windows, I just create a new desktop shortcut, configured as follows:
> >
> >Target: F:\eclipse\eclipse.exe -data
> >E:\Projects\Stellation\eclipse\workspace -vmargs -Xmx256M
> >Start in: E:\Projects\Stellation\eclipse\workspace
> >Run: Maximized
> >
> >As you can see, the "Target" command line has two parameters:
> >
> >         "-data" is used to specify the workspace directory.
> >This is critical.
> >
> >         "-vmargs -Xmx256M" tells the JVM to use 256M of virtual memory -
> >         important when debugging Eclipse plug-ins (i.e. launching a
> >         2nd instance of Eclipse from the development instance), but
> >         maybe not important for straight Java development.
> >
> >The "Start in" field is probably not so critical (since "-data"
> >should be all
> >that Eclipse needs), but it doesn't hurt.
> >
> >"Run: Maximized", of course, makes Eclipse run full-screen.
> >
> >Hope this helps.  Let me know either way; I'll try to think of
> >other things
> >to try if the new workspace doesn't fix it.
> >
> >Regards,
> >Jim
> >
> >At 06:32 PM 10/23/2002, Jonathan Gossage wrote:
> >>I am having a lot of problems trying to understand CVS. As
> >background I have
> >>never used CVS before so I have no background knowledge.
> >>
> >>I created a repository location from within Eclipse using extssh and
> >>verified that I could connect to the repository.
> >>
> >>I then tried to perform the following steps using CVS from
> >inside Eclipse.
> >>
> >>1. I tried to do my first checkin and CVS came back saying that
> >I did not
> >>have write access. I assumed that it had tried to use my
> >original repository
> >>location which used pserver and anonymous login.
> >>2. I then disconnected all the Stellation projects on my local
> >machine from
> >>CVS.
> >>3. I then deleted the anonymous pserver connection, leaving
> >only the extssh
> >>connection.
> >>4. At this point I discovered that the Team menu item was
> >disabled for all
> >>Stellation components. So I did a complete checkout using the new
> >>connection.
> >>5. After this I found that the Team menu item in the resource
> >Navigator is
> >>still disabled aand I am left with no ability to do any CVS
> >related actions.
> >>Does anyone know how I should proceed from here?
> >
> >--
> >Jim Wright, IBM T.J. Watson Research Center
> >*** The Stellation project: Advanced SCM for Collaboration
> >*** http://www.eclipse.org/stellation
> >*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
> >jim.wright@xxxxxxx
> >
> >_______________________________________________
> >stellation-res mailing list
> >stellation-res@xxxxxxxxxxxxxxx
> >http://dev.eclipse.org/mailman/listinfo/stellation-res