In Mars and Neon, Subclipse returns notify.at (or notify.update notify.stats.file.head notify.stats.update) instead of revision number message (like " At revision 1738") on update to head. Works OK in Luna.
This would not be related to Eclipse version. You are probably using SVN 1.9 client and we received a new notification event from the API that we do not have code in place to handle.
Could you file an issue here with some details?
https://github.com/subclipse/subclipse
Related
I'm working on getting my team moved over to Eclipse Juno SR2 and we're currently running Subversion (1.6 server). We're getting the native linux client as well shortly to get us up to client 1.7. I'm seeing some inconsistent behavior with regard to svn:ignore properties.
Currently I've got a multi-module maven project setup (I've got latest version of integrations etc for maven, spring, and other tools). The projects in SVN each have the following svn:ignore property
.project
.classpath
.settings
.springBeans
target
For whatever reason, under Juno with Subclipse 1.8 running the SVNKit client adapter I'm seeing changes showing up under ${project_loc}/.settings and some of the files under target are showing up as "new".
Does anyone have suggestions or ideas? Is this a bug?
Also please PLEASE do not comment that "git, hg, bob's vcs is better than svn, you should switch". I've had that argument over and over and over and I've been shot down continually.
It is a bug. Currently being fixed and should be rolled out next week. If you can rollback your JavaHL or SVNKit plugins to the previous 1.7.8.1 version that will also temporarily resolve it.
I currently face a strange situation, and I have no explanation for it. Here it goes ...
I provide an update site for our company, and to test that update site, I usually do a series of things. One of it is to checkout a special project from Subversion that triggers then a lot of Checkstyle and PMD rules. I use that project since at least 4 years, and it worked all the time like that:
Create a repository location in Eclipse.
Select there the project you want to checkout.
Select from the menu Check Out which uses then defaults to create a new (Java) project.
The resulting project looks like:
Since the new release (testing that with Eclipse 3.7 SR2 Indigo), I get now the following result:
So it looks like the builder(s) are now added to the project name (which seems ridiculous to me). Do I miss here something, is that a feature, not a bug? And is there anything I can do in the configuration of Subversive?
My current configuration is:
Eclipse 3.7 SR2
Windows 7 64bit
JDK 1.7 64bit
Subversive plugin
Subversive SVN Team Provider 1.0.0.I20121109-1700
Subversive SVN Connectors 3.0.0.I20121109-1700
I have added a bug to eclipse, and will document, if there is an answer.
I have added a bug at Eclipse Bugzilla, and the bug was confirmed and fixed. So will wait the bug to be resolved in the public available update site for Subversive.
For a long time my subversion client was working just fine, and I used it for a while out of sts, but one day sts crashed and I rolled back to eclipse for a while and during that time I used subclipse to update a project of mine. Now STS is up and running again, but for some reason now if I ever try to update or commit from sts I get the following error:
The path '{pathname}' appears to be part of a Subversion 1.7 or greater
working copy. Please upgrade your Subversion client to use this
working copy.
There is not actually an available update for subclipse and sts still recognizes the most recently installed subclipse from the dashboard. Any ideas on how to fix this one?
You should be able to install Subclipse 1.8.x in STS. The update site URL is:
http://subclipse.tigris.org/update_1.8.x
That release includes Subversion 1.7 client so you should be all set once you do this.
Subclipse the JavaHL library to do SVN connections. On Windows, if you have the most recent Subclipse it looks like you should automatically have that installed, but if not they have a variety of installation instructions (alas system dependent).
I had integrated a Subclipse plugin into the Eclipse to perform SVN related operations.
I had successfully checked-in, checked-out and commited my project to the SVN.
But now when I am trying to commit or update my project, it is showing the following error
org.tigris.subversion.javahl.ClientException: Unsupported working copy format
svn: This client is too old to work with working copy 'D:\EclipseWorkspace\EMSEclipse'; please get a newer Subversion client
I had tried to update the plugin through HELP >> SOFTWARE UPDATES... of the Eclipse but it is saying that the software is up to date and no newer version is available.
Should I switch to some other SVN Client. If yes, then could you please suggest me any other SVN Client for Eclipse?
Subclipse has different update sites for the 1.4 and 1.6 branches. So if you are using 1.4, it won't have updates. Get the 1.6 update site.
Whenever the subclipse plugin is not sufficient for you, you can download Turtoise SVN - it is a full-featured SVN client.
Subversive is the other Eclipse client for SVN
But for your error, the solution is indeed to upgrade. Did you check the Download and installation process?
As documented, get the right version of JavaHL.
Haven't personally seen that error before. The other popular SVN client for Eclipse is Subversive in-case you want to try that.
I'm using Subversive plugin in Ganymede, but after today's update it stopped working - it just doesn't see any valid svn connectors (I've already been using 1.2.0 dev version of SVNKit, instead of a stable one, because Subversive / Ganymede could not handle it; now it can't handle even the dev one). Any ideas how to make it work? Are subversive guys releasing a new version of their plugin / connectors soon?
I had a similar problem right after the update. It turned out that I had been getting the connectors (the base connector and both the SVNKit and JavaHL connectors) from the Polarion site that had "ganymede" in the URL. Instead, I should have been using the general URL.
Checking my current configuration, you should be using this update URL:
http://www.polarion.org/projects/subversive/download/eclipse/2.0/update-site/
The one I had been using, that should be deprecated if you are using it, is:
http://www.polarion.org/projects/subversive/download/eclipse/2.0/ganymede-site/
Note the difference. Once I changed that, I was able to download the 2.0.3 versions of the connectors, and Subversion again worked for me.
I'm using Subclipse in Ganymede successfully, maybe could you switch? I do recall having problems with SvnKit also, I'm using the JavaHL client.