Can you please step back and just explain again what you are trying to do?
Which of my two scenarios are you trying to accomplish? All of our
previous messages seemed to indicate #2, but now I think it is #1.
Subclipse has a problem working with https:// repositories in that we have
no ability to accept your server certificate. You can solve this by using
the svn command line, and running an svn ls command against your
repository. It should then ask you to accept the certificate and just
tell it to do so permanently.
If you wanted to add your Eclipse project directly to trunk, then the
"trunk" folder cannot already exist in the repository. If you wanted it
in "trunk/project" then you can do this by clicking "Use specificied
project name" and typing that value. It will then create the "project"
folder inside trunk and add to it.
If you already have code loaded in the trunk folder of your repository,
then you should probably be using the Checkout option to initially
populate your Eclipse workspace as a WC associated with Subclipse.
Mark
Eugene Kuleshov <eu@javatx.org> wrote on 01/04/2005 02:17:56 PM:
> Mark Phippard wrote:
>
> Could it be anyhow related to repository structure? I have
> https://host:/repos/projname/trunk and tried to specify "trunk" as a
> module name in share project wizard. SVN repository is locatd at
> https://host:/repos/projname
>
> By the way, it is in windows and I can work with this repository from
> command line SVN or TortoiseSVN tools.
>
> regards,
> Eugene
>
> >Eugene Kuleshov <eu@javatx.org> wrote on 01/04/2005 11:24:00 AM:
> >
> >
> >> In my case Subclipse just deleting all .svn directories if they
> >>already there or complaining that artifact already exists. Am I doing
> >>something wrong?
> >>
> >>
> >There are two "modes" for Share Project.
> >
> >1) New unversioned project to be added to the repository. Wizard
walks
> >you through process of selecting repository provider, specifying
location
> >in repository etc.. This then creates the project folder in the
> >repository, and then checks it back out. This turns your project into
a
> >WC (where everything is unversioned) and you can then add/commit.
> >
> >2) Project is somehow already a valid WC. In this mode, you get an
> >immediate dialog that tells you it found the .svn folders as well as
some
> >other info, such as the target repository. It then offers to "connect"
> >the WC up to Subclipse, which simply does some kind of internal
> >registration within Eclipse.
> >
> >It sounds like you are not getting the dialog in #2, and it is
proceeding
> >down path #1. We should examine why. I am not sure what Subclipse
> >checks. It may just check for a .svn folder in the project root --
that
> >seems most likely.
> >
> >Mark
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
>
_____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management
> Services powered by MessageLabs.
>
_____________________________________________________________________________
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
Received on Wed Jan 5 06:25:54 2005