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

Re: [Subclipse-users] Re: Errant value for svn:keywords?

From: Jeff Chimene <jchimene_at_gmail.com>
Date: Fri, 21 Nov 2008 09:12:19 -0700

Hi Mark,

As for the

I'll try JavaHL. I'm using SVNKit. For some reason JavaHL isn't
installed yet. I'll try to install it.

As for it not being a bug: somehow, the property is set, and it's set
with an errant value. Perhaps that's SVNKit being too helpful. Are you
saying that when I add an element via JavaHL, there are no properties
set? That's certainly better than creating errant values on my behalf.
Is this a pissing contest between JavaHL and SVNKit?

The command script shows that when the value of the property
svn:keywords is "(Id URL)"; which is the value set by subclipse after
adding a new element to a repository, there is no keyword expansion.

As for the observer role, I obviously misread the instructions. Upon
further examination, I now see that such authorization isn't necessary
to file a bug. Feel free to revoke the role.

On Fri, Nov 21, 2008 at 6:48 AM, Mark Phippard <markphip_at_gmail.com> wrote:
> I do not believe there is any chance this is a bug in Subclipse. We
> just call a SVN propset API and if we were inserting ( ) around the
> properties it would show up for any property we add.
>
> Are you able to recreate the problem when using JavaHL as your
> provider? I am not.
>
> If you can recreate it, please provide the steps you took so we can
> try to recreate it. I see you attached a command line script, but I
> do not understand what it is showing. If it helps, I can tell you
> that all Subclipse does is make calls to SVN API's. When you set a
> property from Subclipse it is not like we write data to your working
> copy. We call an SVN API that does it.
>
> I approve all Observer requests, but you should have been able to
> access our issue tracker and even file an issue without. I think you
> only need the role to add comments to someone else's issue.
>
> Mark
>
>
>
> On Thu, Nov 20, 2008 at 11:56 PM, Jeff Chimene <jchimene_at_gmail.com> wrote:
>> Hi,
>>
>> Perhaps this isn't perceived as a bug.
>>
>> I've applied for observer status. Perhaps it'll be granted, perhaps
>> not. The following should be of interest, even to those who don't see
>> this as a problem:
>>
>> TTFN
>>
>> On Wed, Nov 19, 2008 at 3:46 PM, Jeff Chimene <jchimene_at_gmail.com> wrote:
>>> Hi folks,
>>>
>>> I just installed subclipse 1.4.x and want to use svn:keywords.
>>>
>>> I notice that the command
>>> $ svn proplist -v
>>> file:///var/lib/svn/equine/trunk/src/com/public/cgi-bin/equine.cgi
>>>
>>> yields an unexpected value for svn:keywords:
>>> Properties on 'file:///var/lib/svn/equine/trunk/src/com//public/cgi-bin/equine.cgi':
>>> svn:executable : *
>>> svn:keywords : (Id URL)
>>> svn:eol-style : native
>>>
>>> I don't recall setting the keywords in parenthesis (although I suppose
>>> it's possible...)
>>>
>>> I removed the parens and keyword expansion works as expected.
>>>
>>> Any thoughts?
>>>
>>> P.S. I'm will to recreate the repository if that will help
>>>
>>> Cheers,
>>> jec
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
>> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>>
>
>
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
> For additional commands, e-mail: users-help_at_subclipse.tigris.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
Received on 2008-11-21 17:12:35 CET

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.