Mark Phippard wrote:
>> I found why it happens.
>> This projects had been imported by into workspace using existing
>>Eclipse project import wizard. So, it automatically created SVN
>>repository in this new workspace and attached newly imported project to
>>that repository.
>> However it didn't configure repository root url. So, in original
>>workspace svn repository has
>>https://xcommonj-work.projects.dev2dev.bea.com/svn/xcommonj-work url,
>>which is also root and project is located in /trunk/xcommonj. After
>>importing the same project into this new workspace repository created
>>with url
>>
>htps://xcommonj-work.projects.dev2dev.bea.com/svn/xcommonj-work/trunk/xcommonj
>
>>nd root specified. Once I put a correct root it is working.
>>
>> I wonder if Subclipse can import this project with exactly same
>>parameters as the original workspace
>>
>>
>The WC you are importing only has the path to it's URL (the full path). In
>my own testing of this in the past, I found that if you had an existing
>connection that was a subset of the path you are importing, then that is
>the connection it would use. Otherwise, it creates one on the fly that
>points to the full URL. I do not see how it could work any differently.
>
>What version of Subclipse is this? The root URL never returns a null any
>more. If the root is not defined then it returns the full URL. I think
>this was added in 0.9.31.
>
>
It is the trunk version. I was just testing resource patch you've
applied in a separate workspace that did have this repository
registered. So, repository had been created with
htps://xcommonj-work.projects.dev2dev.bea.com/svn/xcommonj-work/trunk/xcommonj
path and root usrl appears to be the same. Sorry for the confusion.
regards,
Eugene
Received on Fri Aug 19 23:56:39 2005