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)
Related
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.
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
I am looking to build a website in GWT top replace a couple of desktop apps we have here at work, I programmed in java 12 years ago so the code should not be a problem.
I am having problems with installation GET and Eclipse.
I seem that when you use the latest version of Eclipse (Juno 4.2) and try to use the GWt Plug in the installer process fail looking for very specific versions of libaries.
My question is "Is there a recommended version of eclipse and GWT that is not on the cutting edge and I can get to work with relative ease"
I hope this will help you for using GWT in Eclipse
Use this. Get the newest Eclipse "Juno" and choose the standard java version.
Now you need to use the proper link for the plug in. For Juno it is 4.2. If the guide in the link doesn't work, check your firewall.
Found the problem I used the standard and java versions of eclipse.. if you using the J2EE version everything runs as normal
I have gone through with the tutorial documents for blackberry development.
At every place they have showed the features with eclipse plugins.
So, I would like to know that which are the tools I need to download If I want to start development using NetBeans 6.8 (or 6.5) ? And what is the procedure to do so ?
Thanks in advance...
One guy called Jonathan Fisher did come up with a solution, but his page disappeared off the web a while ago. But I managed to find it using the Wayback machine to get the archived webpage.
Basically you need to first install the Blackberry JDE (which is Eclipse based), then in Netbeans Mobility settings go to Manage Emulators and do Add Plaform in the platforms manager to add a custom platform that points to your Blackberry JDE directory, and remove all the automatically added jars except for net_rim_api.jar
Next, when you start a MIDP project, select your new custom Blackberry platform as your emulator in the project settings. You will also need to add some custom build settings to build.xml, plus a Blackberry .alx application loader file to the project. It's a bit long-winded, so best to follow the instructions as per the aforementioned link.
There are no plugins that are available for BlackBerry development on Netbeans. But, you can do so, if
you are willing to give up the on device debugging that you can get with Eclipse plugin.
And are willing and know how to install BlackBerry JDE in Netbeans.
The advantage here is Netbeans has a lot more sophisticated preprocessor support, whereas BlackBerry plugin in Eclipse has rudimentary support for that.
I have wrote a short article on this on my blog link text
, it tells you how to confguire Netbeans for BB development.
this is only supporting J2ME not cldc .
I would highly recommend using the Eclipse plugin. Its supported from RIM and it has a large enough community base for troubleshooting.
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...