[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 17:37:46 -0400


There appears to be a problem with walking the tree to the repository root in search of the bugtraq properties. I have a number of projects in my workspace, and most of them fail to display the issue number box on commit.

Here's what I see: I exported the bugtraq properties as a set from /project/trunk/foo and imported them into one of these project directories (the directory where .classpath and .project live). Suddenly, I got the issue number box when I tried to commit changes in that project.

Also, the issue number box appears consistently from TortoiseSVN at all locations in /project/trunk/foo without the need to add the bugtraq properties at any other level. This problem only exists inside Eclipse when using Subclipse. From everything you've said (and written elsewhere), I understood that there should be no difference in bugtraq-based property behavior between TortoiseSVN and Subclipse. In my particular instance, that does not appear to be the case. If I had set the properties incorrectly (certainly a possibility), I would expect it not to work from TortoiseSVN as well.

Any suggestions?


Michael Schechter

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

On Fri, Mar 27, 2009 at 4:30 PM, Schechter, Michael
<MSchechter_at_national.aaa.com> wrote:
> Mark,
> /trunk/foo does not live in my workspace. My workspace lives parallel to /trunk/foo.
> My structure is:
> /project
> /trunk
> /eclipse (workspace lives here, only has references to projects as we don't copy into workspace)
> /foo (Eclipse projects/code live here)
> Also, we import all projects from the "foo" tree, rather than checking out into the workspace.

I still do not really understand this part. Not sure I need to.

> As of now, the "Issue #" prompt is working correctly from both the package and project explorer
> views within the Java perspective. Given that you say this should not work, I am very confused.

When did I say that! I am quite certain I did not. It should work
from everywhere.

> This does not match to any of the attempts I have made to start a commit, and instead seems to
> be related to Eclipse software updates. I was able to determine that a similar block was written
> when I checked for Mylyn updates.

Yes, nothing to do with Subclipse.

> org.tigris.subversion.subclipse.graph.popup.actions.SynchronizeViewGraphAction
> !STACK 0
> java.lang.NullPointerException

This might be causing problem, but it is not directly related. It is
just determining whether to show the Revision Graph option. The
latest version of the Revision Graph plugin fixes this. You can try

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