Ronald Sacher <firstname.lastname@example.org> schrieb am 04/12/2005 12:54:39 PM:
> Hello Jan,
> am Dienstag, 12. April 2005 um 12:43 schrieben Sie:
> > I did install it first but alas, without fun. The checked out project
> > appeared not under version control (all files are decorated with
> > marks), and when I clicked on individual files and tried "Add to
> > Control", I got an error message.
> > Then my impression was that the JavaSVN plugin was not the "official"
> > way to use Subclipse (there are mentions of unimplemented features),
> > and I got stuck with JavaHL.
> What I read here is that JavaSVN is the easiest way to use Subclipse
> on Linux.
> I head the same problem getting started. I think I got around that with:
> - Create repository location with Subclipse
> - Create remote folder. Let's say "test"
(This was done for me by an admin.)
> - Use Cmdline for initial checkout
> * cd to your project
Do you mean that I should create a "Simple" project with "New Project"
first and cd into the project's directory? Or should I check out the
thing into my workspace and then make it known to Eclipse by creating
> *> svn co http://repositoryserver/location/test
> - Do "Refresh" in Eclipse
I tried both ways mentioned above and in either case, the project did not
become version controlled after a Refresh. I also tried "Team/Share
which led me to the Team Synchronize perspective (as expected), but did
make the project shared in the end (i. e. no decorations for files, no SVN
mentioned in project properties, Team/Share Project... still available
Anyway, thanks for the hints.
Best regards -
Received on Tue Apr 12 21:43:27 2005