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

Re: [Subclipse-users] Question about bugtraq properties

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 31 Mar 2009 14:01:17 -0400

On Tue, Mar 31, 2009 at 11:19 AM, Schechter, Michael
<MSchechter_at_national.aaa.com> wrote:

> Two things I want to leave you with:
> 1) The behavior issue that I am seeing appears to be related to the atomic commit behavior that
> we discussed last August, and that you fixed in bug 783. It still seems very odd to me that the
> behavior is inconsistent.

They are not really related at all, other than that the directory
layout is the same. The bottom line is that 99%+ of our code uses
Eclipse API for stuff and Eclipse does not know about things outside
the workspace. I think it is reasonable when we are using Eclipse to
crawl your project to stop at the project. Our only alternative would
be to switch to the Java IO classes for this.

The commit change was just a hack where it checks to see if the common
root folder of a commit is a WC or not. That mostly happens in the
SVN code. Hopefully this will become native to SVN in 1.7, as I am
sure the hack is going to stop working then one way or another.

> 2) In the cases where Subclipse correctly detects the bugtraq properties, there is a minor
> problem with the URL it builds. Our bug format is "Issue Number %BUGID%:\n", and when
>Subclipse displays the hyperlink in the history view, it includes the ":" as part of the link
>(TortoiseSVN does not do this). The resulting link tells me that bug "355:" does not exist. Is this an
> issue with Subclipse?

It sounds like it. Can you file an issue with all of your bugtraq
properties, a sample log message and the URL it uses?

Mark Phippard
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-03-31 20:01:37 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.