[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] JavaHL vs SvnKit behavior on multiple-project checkins.

From: Steve Cohen <scohen_at_javactivity.org>
Date: Mon, 04 Aug 2008 18:45:55 -0500

Mark Phippard wrote:
> On Mon, Aug 4, 2008 at 6:20 PM, Steve Cohen <stevecoh1_at_comcast.net> wrote:
>
>> When using Subclipse and Eclipse 3.3 and making commits across projects,
>> with SvnKit I get all projects getting the same revision number (which is
>> what I want, since the individual projects are logical units and the commit
>> is atomic). When using JavaHL, each project is treated as a separate
>> commit. Why the difference?
>>
>> I was puzzled by this for some time until I realized that this was the
>> difference between two workspaces.
>>
>
> Subversion does not support this at the API level and JavaHL is part
> of Subversion. SVNKit made an enhancement in this area and added a
> special API we use.
>
> In Subclipse 1.4.x we have added our own "hack" so that this also
> works with JavaHL,
>
> The current version of Subclipse is 1.4.2. There is an additional
> optimization to this hack coming in the 1.4.3 version, but I am
> guessing you are just using 1.2.4.
>
>
>
Eclipse tells me there are no updates past 1.2.4. What must I do to
allow it to see this version?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-08-05 01:46:29 CEST

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.