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

Re: [Subclipse-users] tsvn:logtemplate

From: Stephen Elsemore <selsemore_at_collab.net>
Date: Wed, 19 Feb 2014 10:49:48 -0800

As of http://subclipse.tigris.org/issues/show_bug.cgi?id=1511 Subclipse has
fount the tsvn:logtemplate property (and other tsvn properties) like this:

svn proplist <location> --show-inherited-props

where <location> is the location of the first resource in the list of items
being committed.

Prior to the #1511 change, the logic was similar except that Subclipse
walked the working copy itself, starting with a resource being committed
and going up through the parent folders.

This seems to be working correctly for me. You might try running proplist
from the command line to help determine why you are not getting the
expected results:

svn proplist <location> --show-inherited-props --verbose


On Mon, Feb 17, 2014 at 6:15 AM, Lorenz <lorenznl_at_yahoo.com> wrote:

> Hi all,
> seems like subclipse picks up the wrong tsvn:logtemplate on commit
> (again 8-)
> Subclipse (Required) 1.10.3
> Subclipse Integration for Mylyn 3.x (Optional) 3.0.0
> Subversion Client Adapter (Required) 1.10.1
> Subversion JavaHL Native Library Adapter 1.8.5
> on further testing there may be more, but for now:
> 1) commiting from the project root folder picks up the
> tsvn:logtemplate of the parent folder in the repository not the one
> set on the folder associated with the project root.
> 2) a child folder of the project root, having no own tsvn:logtemplate,
> shows no template at all (this folder is used to for several
> svn:externals including file externals)
> 3) folders directly under the project root pulled in via svn:external
> also pick up the same tsvn:logtemplate as 1) instead of their own.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2014-02-19 19:49:55 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.