[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: Fri, 27 Mar 2009 15:10:56 -0400

On Fri, Mar 27, 2009 at 2:54 PM, Schechter, Michael
<MSchechter_at_national.aaa.com> wrote:

> Until recently, I was not aware that Subclipse supported the bugtraq
> properties.

We have always supported them. We co-wrote the design with TortoiseSVN.

> When I went to commit a Mylyn changeset today, I saw the “Issue
> #” box in the commit dialog for the first time.
> I subsequently upgraded to Mylyn 3.1 from Mylyn 3.0.4, and I cannot
> reproduce the circumstances under which the bug number is prompted for. I
> also cannot get Eclipse to revert the configuration so that I can use Mylyn
> 3.0.4 again, although I am not certain if Mylyn is the source of the
> problem.

I would not think it would matter. I do not suggest you try to revert.

> My understanding is that even through Mylyn, the commit dialog is
> managed entirely by Subclipse.

This is true.

> Our bugtraq properties are set on a directory that lives directly under
> trunk (/project/trunk/foo), and our source tree lives under that. The “Issue
> #” prompt works at all levels of the source tree if we use TortoiseSVN.

The directory should just have to live in your workspace. In the
Synch view it is easy to bring up a commit that has items for multiple
projects. Is it possible that is happening?

What happens if you do Team > Commit on the Project from the normal
project explorer view?

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