[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: Schechter, Michael <MSchechter_at_national.aaa.com>
Date: Fri, 27 Mar 2009 15:55:49 -0400

Mark,

When you say "The directory should just have to live in your workspace," which directory are you talking about? The directory with the bugtraq properties? My workspace is parallel to that directory ("foo"), and the projects are all referenced under "foo".

When I saw the "Issue #" prompt, the commit from the Synch view was across two projects. I have tried to duplicate the circumstances under which it appeared without success.

I get the same behavior regardless of whether I am in the Synch view or the Java package explorer view. However, it works correctly (as described in http://markphip.blogspot.com/2007/01/integrating-subversion-with-your-issue.html) if I use the *project* explorer. I don't normally have that view open, so I just opened it to verify behavior.

Once I get it working in the project explorer, it works correctly in the package explorer, even if I then close the project explorer. However, it still *refuses* to work in the Synch view, which is where I first saw it work.

Any idea why I'm seeing the discrepancy?

Thanks for the help!

Michael Schechter
mschechter_at_national.aaa.com
RESPONSESupport_at_national.aaa.com

-----Original Message-----
From: Mark Phippard [mailto:markphip_at_gmail.com]
Sent: Friday, March 27, 2009 3:11 PM
To: users_at_subclipse.tigris.org
Subject: Re: [Subclipse-users] Question about bugtraq properties

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?

--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1447489
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
This communication (including all attachments) is intended solely for
the use of the person(s) to whom it is addressed and should be treated
as a confidential AAA communication.  If you are not the intended
recipient, any use, distribution, printing, or copying of this email is
strictly prohibited.  If you received this email in error, please
immediately delete it from your system and notify the originator.  Your
cooperation is appreciated.
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=1447915
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2009-03-27 20:56:44 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.