Subclipse DEAD

[MattSchultz]

I have the latest version of Aptana (just downloaded yesterday). I tried to get all the plugins (PHP, Rails, AIR, iPhone, and Subclipse). All plugins install fine, and all other plugins run fine.

But the minute I try to do anything involving SVN (even loading a project with SVN bindings, or opening a subclipse screen) Aptana crashes hard.

Anyone else have this problem?

[btaylordesign]

I second that. I don't have issues on Mac OS X, just Windows XP.

Here is the error I receive:

JVM terminated. Exit code=1
C:\Program Files\Aptana\Aptana Studio\jre\bin\javaw.exe
-Xmx384M
-Xms128M
-Djava.awt.headless=true
-jar C:\Program Files\Aptana Studio\startup.jar
-os win32
-ws win32
-arch x86
-launcher C:\Program Files\Aptana\Aptana Studio\AptanaStudio.exe
-name Aptana
-showsplash 600
-exitdata 1794_80 C:\Program Files\Aptana\Aptana Studio\AptanaStudio.exe Studio
-vm C:\Program Files\Aptana\Aptana Studio\jre\bin\javaw.exe
-vmargs
-Xmx384M
-Xms128M
-Djava.awt.headless=true
-jar C:\Program Files\Aptana\Aptana Studio\startup.jar

[khakman]

So that we can look into this more, please submit a bug report via http://support.aptana.com/asap. There, please provide more info (e.g. version of studio, running standalone or in eclipse, which version of eclipse, etc...)

Thanks.

[MattSchultz]

I second that. I don't have issues on Mac OS X, just Windows XP.

Here is the error I receive:

JVM terminated. Exit code=1
C:\Program Files\Aptana\Aptana Studio\jre\bin\javaw.exe
-Xmx384M
-Xms128M
-Djava.awt.headless=true
-jar C:\Program Files\Aptana Studio\startup.jar
-os win32
-ws win32
-arch x86
-launcher C:\Program Files\Aptana\Aptana Studio\AptanaStudio.exe
-name Aptana
-showsplash 600
-exitdata 1794_80 C:\Program Files\Aptana\Aptana Studio\AptanaStudio.exe Studio
-vm C:\Program Files\Aptana\Aptana Studio\jre\bin\javaw.exe
-vmargs
-Xmx384M
-Xms128M
-Djava.awt.headless=true
-jar C:\Program Files\Aptana\Aptana Studio\startup.jar

Second the error report. That's what I get.

[khakman]

please submit a bug report via http://support.aptana.com/asap.

by submitting a bug report it'll go right to the folk that can address it for you (plus you'll get notified as progress is made on the issue if an immediate workaround is not available)

[btaylordesign]

Ok, I opened a ticket for this issue.

Thanks,

[MattSchultz]

I have an update on this bug:

I recently purchased a new computer (a MacBook Pro ), and, after installing the following items (all, except windows, are latest downloads from the web - I never store downloads), in sequence, Aptana works fine*:

-- Windows Vista SP1
-- Several unrelated softwares, like browsers
-- Ruby 1.8.6 using the one click installer
-- Fully updated gems
-- Gems: rails, mongrel, mysql, capistrano
-- TortiseSVN
-- Aptana
-- RadRails, PHP, Air, and iPhone plugins
-- Subclipse plugin

* Actually not quite. When I do interesting things with SVN (particularly setting properties it seems, though I haven't completely isolated that), Aptana sometimes throws an error telling me that I have an outdated version of SVN which cannot handle the repository format any more. Since TSVN always is able to, I figured there must be a copy of SVN in subclipse, and that by installing a full copy of SVN on my system, I would be able to solve this problem.

So I did. I grabbed and installed the tigris build of 1.4.6 (since they didn't have a 1.5.0 build) for Apache 2.2 (note I do not have apache anything installed - I just figured using the latest would be best). It installs great, and doing 'svn --version' in my cmd now shows it (though I don't know what it was showing before). Started up Aptana, which then opens my project, and bang, it crashes with this error.

So that may provide some more information as to what is causing what....I will try uninstalling my packaged svn and see if that saves Aptana.

[MattSchultz]

Yep, Uninstalling saved the day.

A few more notes:
-- TSVN claims to be version 1.5...this may have something to do with it.
-- 'svn --version' now fails, there is no instance of svn in the path.

I just installed a 1.5 version of SVN (apache 2.0 this time) and everybody works. But it doesn't solve the problem in Aptana regarding the older client. So somewhere, somehow, there are two svn clients going on here.

I was able to make Aptana happy again by re checking out my working copy after committing everything with TSVN. Not the smoothest workflow here, but at least it is all working again.

[MattSchultz]

I believe I have found the end-all solution to SVN.

The problem with subclipse is not subclipse, it is Aptana. Specifically, the update site that Aptana includes for Subversive only includes up to version 1.2.4. A quick browse to their website (stupid me for not doing this before) shows that in fact the latest version is 1.4, and 1.2 versions are depreciated and no longer supported. This would clearly explain why it doesn't work.

I'm re-building aptana now one last time...this time everything SHOULD work!

It WORKED! Subclipse 1.4 solves the problem nicely!

[c1cculloh]

How do you install Subclipse 1.4 on Aptana?

I added a new remote update site:

http://subclipse.tigris.org/update_1.4.x

to my Update manager. When I tried to install it, it told me I needed Mylyn 3.0.0. So I after much searching I found Mylyn 3.0.0 and added another new remote update site:

http://download.eclipse.org/tools/mylyn/update/e3.3

to my update manager. Then when I tried to install that, it told me I needed org.eclipse.ui 3.3.0 or equivalent. How do I get that? Am I going down the right path? Do I need to reinstall Aptana or something?

Thanks!

[blazar]

The current release of Aptana Studio is built on Eclipse 3.2, which is why you're seeing that needs 3.3 error message. We are working on a new version built off 3.4 base but for now the workaround is to install Eclipse (3.3 or 3.4, probably the latter is better) and install the plugin version of Studio.

[MattSchultz]

Just disable the Mylyn integration, and subclipse will install.

Aptana - this shouldn't be this hard - it should just work automatically. Please fix this. Build a 3.4 based version, fix the plugin, etc. Whatever. But small bugs like this are a gross distraction - a demonstration that you don't care enough about your services to assure a smooth user experience.

Good luck,

//Matt

[jtara-sny]

Subversive, though, seems to be the flavor of the day - it's in incubation to be the "official" Eclipse SVN client and is now distributed by eclipse.org, while Subclipse remains a third-party plugin distributed independently.

I've been using Subversive with Aptana both installed as plugins to Eclipse 3.4 with no notable problems or crashes in Subversive.