Possible to do GWT 2.2 Maintenance in Eclipse Kepler? - eclipse

I have the task to do some work on our GWT 2.2 code base with
the GWT Config, etc, used, is long gone. And I must use Eclipse Kepler.
Does current GWT provide backward compatability that far?
Any thoughts?

The version of the Eclipse plugin is independent of the version of the SDK you use in your project. You can use the newest plugin with GWT projects that needs older versions of the SDK.
You have to set this up in the project properties.

Related

Using old version of GWT SDK with Eclipse Luna

we have a project which is compatible with GWT SDK 2.4 and Eclipse Indigo. I am trying to move to Eclipse Luna. Although I have made a progress, I couldn't get all of the features yet. Here is what I've done:
Downloaded Eclipse Luna and JDK 1.7 (both 64 bit)
Using install new software, installed last version of GWT SDK and
designer
Downloaded GWT SDK 2.4
Set this SDK as default (I copied some jars from SDK 2.6 in order to
do this)
After this installation, the project succesfully compiled and debugged. In addition, there are no problems with GWT Designer with my old ui.xml files. However, when I try to add new page I realized that Add New MVP view is gone. Is there a way to bring back this feature? Or can I copy from old Eclipse plugins?

Eclipse Luna without built-in plugins

Eclispse Luna has been just released. I wanted to grab it from the download site. But here comes my problem. Even the Standard and Java Developer versions have features built-in which are not needed for me and just slows down the IDE. For example i do not use Mylin or Plug-in development. These things cannot be deleted from the installation... Is there an Eclipse Luna release which only contains the basic package?
Look at the Eclipse Project downloads
The Eclipse Platform is the smallest (but does not even have Java development).
The Eclipse SDK has Java and Plugin development and the Eclipse source. This is the one I always start from.

Migrate Eclipse 3.3 features/plugins to Eclipse Juno 4.2

I'm using an old version of Eclipse (Eclipse Platform 3.3) which uses a product comprising a large number of features and plugins. The product vendor is no longer in business so I'm looking at the viability of migrating the features/plugins to run on Eclipse Juno 4.2. The JAR files in the plugins were compiled on Java 5 and will be running in a Java 7 environment (no source code). Has anyone had any experience of doing such a thing, is it possible and is there any reference material? I really can't think of any more detail to add to this question, so I'm going to go with this.
Thanks.
Do you have an update site for the features? If so, did you tried to install the feature/plugins on a fresh eclipse 4.2?
If you can identify the files in plugins and features folder of the product you try to use with 4.2, did you tried to copy them on the plugins/features folder of a clean 4.2?
Eclipse 4 application platform provides a compatibility layer for 3.x plugins, so it may just work.
http://xseignard.github.com/demoCamp2012/prez/#22
You can also find some literature about migrating 3.x plugins to 4.X there : http://www.vogella.com/blog/2012/11/13/getting-your-eclipse-plug-ins-ready-for-eclipse-4/
Regards

one eclipse Indigo and two GWT SDK versions

I decided to install GWT 1.5 in addition to installed GWT SDK 2.3; I've never had two GWT SDK on one IDE before... The question is...
Won't the two SDKs conflict if I have them both?
No you can easily have multiple SDKs installed. You can select the one you want to use for your project in the project properties (In Eclipse: Google->Web Toolkit->Use specific SDK)
You can have as many. You can set the default GWT SDK in Preferences->Google->Web Toolkit or you can override this per project (Project->Properties-Libraries)

Developing on Eclipse 3.4, running on Eclipse 3.3

I'm developing an Eclipse plug-in, based on a bunch of core Eclipse plug-ins like SWT, JDT, GEF and others.
I need my plug-in to be compatible with Eclipse 3.3, since many potential customers are still using it. However, personally I like the new features in Eclipse 3.4 and would like to use it for my development. This means I need PDE to reference 3.3 code and, when debug, execute a 3.3 instance.
Any tips on how this can be achieved?
Thanks.
You can change the 'Target platform' setting to point to the location of an existing set of eclipse 3.3 plugins. This will compile your code against the 3.3 plugins, making sure that they stay compatible no matter which version of eclipse you are using to develop the application.
The setting is under Window->Preferences->Plug-in development->Target Platform
What Barak said. See also this topic on Eclipse help:
http://help.eclipse.org/stable/index.jsp?topic=/org.eclipse.pde.doc.user/guide/tools/preference_pages/target_platform.htm
Note also:
the default target platform is your Eclipse install
your dev environment should be at least as recent as the target platform (i.e. you cannot use 3.3 as dev environment and target 3.4)
this also allows you to develop against plug-ins you don't have in your development Eclipse install.
And is it no way how to develop plugin for newer palfrom? Eg.: develop new plugin for 3.5 into 3.4...