Thanks for your fast and qualified response.
> This is an eclipse limitation when a plugin contains JAR's. You would
> have to checkout our plugin (use the 1.2.x branch, and then this will
> go away).
I already did that (Ok, in a different workspace ^^). So I understand,
that I have to create a Project Dependency from my Plugin-Project to a
fresh checkout of the subclipse (source) Project, right?
>> Question 2:
>>
>> Is it possible to use different svn Repositories within only one
>> Project? The "Share Project"-Wizards makes me fear not, but why?
>
> No, you cannot. However, Subversion supports this natively by using
> the svn:externals property to pull in code from other locations. Just
> add a property like this to the lib folder:
>
> name: svn:externals
> value: lib-dirA url://reposA/lib
> lib-dirB url://reposB/lib
Thanks again for this detailed explanation. Some minutes ago, I tried to
share a Project first (Repository A) and then committed (via
svnClientAdapter) some directories to a different repository (B). ->
This worked without any problems. Subclipse didn't seem to care, I was
still able to add files (to Repository A) and commit / update files. Is
this workaround discouraged?
Cheers,
Konrad
Mark Phippard schrieb:
> On Wed, Mar 5, 2008 at 9:27 AM, Konrad Jünemann <K_Juenemann_at_gmx.de> wrote:
>
>> Question 1:
>>
>> I'm writing an Eclipse Plugin which uses (or should use) Subclipse. So I
>> added "org.tigris.subversion.subclipse.core" to my required plug-ins.
>>
>> Problem: I'm unable to import any classes from
>> org.tigris.subversion.svnclientadapter.*
>>
>> Error: "The import org.tigris.subversion.svnclientadapter cannot be
>> resolved"
>>
>> Other classes like org.tigris.subversion.subclipse.core.SVNClientManager
>> are correctly imported. Now I wonder what I am doing wrong, since
>> org.tigris.subversion.svnclientadapter is marked as an exported package.
>> Does it matter, that it is imported by subclipse.core as a jar?
>>
>> Any ideas?
>
> This is an eclipse limitation when a plugin contains JAR's. You would
> have to checkout our plugin (use the 1.2.x branch, and then this will
> go away). BTW, the next release has an all new architecture and
> svnclientadapter is now a plugin itself. This is reflected in our
> trunk.
>
>> Question 2:
>>
>> Is it possible to use different svn Repositories within only one
>> Project? The "Share Project"-Wizards makes me fear not, but why?
>
> No, you cannot. However, Subversion supports this natively by using
> the svn:externals property to pull in code from other locations. Just
> add a property like this to the lib folder:
>
> name: svn:externals
> value: lib-dirA url://reposA/lib
> lib-dirB url://reposB/lib
>
> etc..
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-03-05 16:51:01 CET