products forums blog support careers about
  History | Log In     View a printable version of the current page.  
PRO USERS, to ensure 'PRIORITY SUPPORT' make sure that your ASAP account is "tagged" when you file the request. Click here for instructions on how to tag your account.
Issue Details (XML | Word | Printable)

Key: STU-680
Type: Enhancement Enhancement
Status: Reviewed Reviewed
Priority: Critical Critical
Assignee: Ingo Muschenetz
Reporter: Chris Williams
Votes: 17
Watchers: 9
Operations

If you were logged in you would be able to see more operations.
Aptana Studio

Use Eclipse 3.4 as the base platform

Created: 12/Dec/07 10:34 AM   Updated: Tuesday 11:29 AM
Component/s: None
Affects Version/s: Aptana Studio 1.0.2
Fix Version/s: Aptana Studio 1.x

Issue Links:
Depends
 

Importance: Critical
Studio Install Type: N/A
Participants: Bob Weston, Chris Williams, Ingo Muschenetz, Louis-Rémi BABE and Scott Bronson


 Description  « Hide
I know we've discussed this in the past, but we're very behind on the base platform we use to build and target Aptana products. Eclipse is now on Milestone 3 of Eclipse 3.4; and Eclipse 3.3 final has been out since June.

Most of our users who use us as an Eclipse plugin use us on 3.3, and until we target that version there will be a number of incompatibilities. For example, in RadRails we cannot provide evaluation of arbitrary expressions under the debugger because Eclipse moved (rather than deprecated) a set of debug APIs between 3.2 and 3.3.

We'd also be able to take advantage of UI and other improvements in the base platform.



 All   Comments   Change History      Sort Order:
Scott Bronson - 18/Dec/07 06:50 PM
Also, 3.2 has some pretty serious problems on the Mac and 64-bit Linux platforms. 3.3 works beautifully on both. That's why I'm personally struggling to run Aptana/RadRails on top of 3.3. I can't wait until Aptana ships on 3.3.

(just a thought... If this issue hasn't been resolved by April, it might be a good idea to go straight to the 3.4M series... 3.4 is due in June.)


Scott Bronson - 01/Apr/08 12:34 AM
It's April! 3.4M6 is out: http://download.eclipse.org/eclipse/downloads/drops/S-3.4M6-200803301350/index.php

Any chance someone could update this bug with a target for when you'll update the platform? 3.2 is starting to seem quite obsolete...


Chris Williams - 17/Jun/08 10:19 AM
Given that Eclipse 3.4 is now in Release Candidates (I think RC3 at this point), it doesn't make much sense to use Eclipse 3.3 as our base target, but to target 3.4 and be backwards compatible with 3.3 as much as possible.

Louis-Rémi BABE - 27/Jun/08 06:40 AM
Eclipse 3.4 is now out !

Bob Weston - 01/Jul/08 11:29 AM
Is there a list being kept somewhere of what does not work on Ganymede?

I don't use RadRails, but the only real "blocker" for me currently (the only thing that, so far, I care enough about that I won't switch to 3.4 until it works) is the Aptana File Search. Everything else that still seems to be an issue out of what I use I seem to be able to work around by keeping a 3.3 installation, installing plugins there, and copying plugin and feature files over manually.