Our project uses gwt 1.7 and jdk 1.5.0_13.
We need to add support for IE9 and above.
For that, we need to upgrade gwt to latest version (2.5) and, therefore, upgrade jdk as well.
While doing so, we are getting errors related to missing source codes in gwt jars (e.g. TimeOutException source code not found).
We have simply replaced the gwt 1.7 jars with latest ones. What else do we need to change?
Is there any guide explaining the migration procedure for gwt?
AFAIK there isn't any detailed guide explaining the migration. In the documentation project you have only a brief list of features and breaking changes for each version, it is very useful though.
You have many posts with the experience of users migrating from 1.7 to 2.0, but almost very old since 2.0 was released some years ago. There is very little info for migrations from 1.7 to the the last 2.5.
Said that, the main problem you will deal with is the change in the tools for dev and debug, so I recommend first to get used with these tools. Then you have to fix each single 'red' mark in your IDE project. Then you should look for 'yellow' marks in order to avoid using deprecated classes/methods. Finally you could consider replacing some code of your project with new features in 2.x like cell-widgets, layout-panels, etc, see the showcase.
The process will be tedious, but it is worth to have your project using last releases if you plan to maintain the application in the future.
BTW, there are plans to remove support for IE6, IE8 and even IE9 in future versions of GWT, in order to improve and modernize gwt and to support new html5 features. It will be gradual though: Solutions for people needing IE7/IE8 support in future GWT releases
I updated from 2.2 -2.5 yesterday and had 2 errors I had to overcome.
Jar file was for 2.2- I deleted it, switched to non GWT toolkit, and switched back. This updated(created) to correct jar.
source code problem- for some reason the run config was not transferred correctly. Since i had used a new workspace when updating i copied over the old path to the new workspace. (this was located under: Debug config--> Arguments--> Program arguments
Hope this helps :)
Related
I have been using ANTLR with Eclipse for some time using the ANTLRv3IDE plugin. While it is not perfect, and a bit outdated, it does its job reasonably well.
Now I am looking to switch to ANTLRv4 for another DSL that I am creating. However, Eclipse support seems to be extremely thin. I decided to try out ANTLRWorks, which is a NetBeans plugin, but I could not get it to install (it seems to be locked to specific dated versions (201302132200 while I have something newer, still 7.3 as docs say) of dependencies).
So, the question: Has anyone set up any Java IDE (preferably Eclipse, but I could be persuaded to switch if support is good for something else) to integrate with ANTLR? With integrate, I mean: code generate on save/keyboard shortcut and syntax coloring (at the very least). Code completion and other features are of course nice to have, but I could live without them for now.
I am well aware of Xtext and I have had great success using it for some projects, but unfortunately it does not fit the needs here (need no IDE support, need my own DSL model not based on ECore, etc).
I know ANTLRWorks can be run as a standalone application without a Java IDE, but that I consider to be a last-resort solution as it is extremely cumbersome to work this way (switch between application, files out of sync, no VCS support etc). I tried the other way around: to install the Java parts into ANTLRworks (which itself is a NetBeans distro), but it did not end well (it seems basic project support etc was stripped out of ANTLRworks).
Antlr4 plugin for Eclipse is here:
https://github.com/jknack/antlr4ide
ANTLRWorks 2 uses many non-public interfaces from NetBeans, which means it will always be bound to a particular version. The standalone download will always work because it bundles the dependencies itself.
The standalone build of ANTLRWorks 2.1 is available. This build includes support for ANTLR 4.1.
A new plugin build of ANTLRWorks 2.1 will be available once NetBeans 7.4 is released.
Moving forward, the code for ANTLRWorks post-2.1 is open-source under an LGPL license.
I think you have downloaded Netbeans 7.3.1.
Try download 7.3 from https://netbeans.org/downloads/7.3/ and install the ANTLRworks plugin there. (Link to the ANTLRworks Update Center: http://tunnelvisionlabs.com/downloads/nbupdates/nb73/aw2/updates.xml ).
Note that ANTLRworks v2 contains ANTLR v4.0, which is not the current version of ANTLR (4.1). So also download ANTLR v4.0 from the ANTLR download folder (The antlr-4.0-complete.jar file) and use it as library for compilation.
Now you can use nearly all things you wanted.
ANTLRv3IDE was opensourced. It should be compile-able for Juno. For stringtemplate (ST4) look at the Hastee plugin. It supports some of ST4 constructs.
I recently switched from Eclipse to Netbeans 7.3 and experiencing a lot of quirks and i'm wondering if anyone else experienced them and/or got a solution. Because of these 'problems' i'm considering switching back to Eclipse again but i'm in doubt because NB has a lot of good things too !
These are the quirks:
when creating a new Java class, and make some typo's e.g. somewhere in a method, NB does not recognize / display the errors directly, but after a very long wait or a restart of NB.
This also happens to existing classes.
background scanning tasks is sometimes stuck at 100%
code completion does take forever. Don't even think about refactoring or renaming a class because it takes >3 minutes to scan the classpath (why, it's a new class for crying out load)
hot-deployment: changes are not always synchronized correctly with the (Glassfish) server.
Sometimes a complete undeploy and deploy is needed to reflect the changes made in the source.
NB manipules my pom.xml and glassfish-web.xml: it adds a deploy hint to the pom.xml and also changes or removes the context-root in the glassfish-web.xml. Please stop doing this!
Why o why can't i do a 'Fix imports' on my entire project. You can do a 'organize import' on the entire project, but this won't add the missing imports. See http://netbeans.org/bugzilla/show_bug.cgi?id=167031#c2
Running NB 7.3 on Windows XP, 3GB RAM, 2+GHz cpu
The project is a Java 7 maven project containing 12 modules / sub projects
I strongly recommend that you DO NOT attempt to install the ScanOnDemand plugin. It completely trashed my Netbeans, forcing me to use the Task Manager to kill the process. No existing projects were found; they were all listed as "unrecognized project; missing plug-in?". I had to re-install Netbeans.
One thing to look for is max heap allowed. Try adding "-J-Xmx2000M" to the Netbeans startup.
ref: Setting Heap Size
I suggest stick to your favourite IDE. Eclipse is still popular and Juno packages are doing good and Kepler is already available. You can try around latest packages.
IntelliJ IDEA looks better than other Java IDEs (light weight, faster, nice integration with SCM(source configuration) tools, possibility of easy cloud deployment, except that if you have freedom to choose your IDE whether you are part of a big/small teams, Otherwise there is no need to shift from one to other.
IntelliJ is the first IDE to give nice in-built support to Play framework
Google Android ADT is completely moving towards AndroidStudio based on community version of IntelliJ IDEA for faster and better GUI and app development.
As a Java developer it is not bad to try the other IDE to do some experiments or for any reason it strikes your mind.
Eg: Netbeans comes with sample apps in Java EE,Java7/Java2EE which looks better, nice examples for websockets, Servlet3.0, NIO examples etc,...but just try it or just ignore if it does not work. It is very easy to generate Entities from Database Tables, creating REST Endpoints in NetBeansIt may come with lot of in-built plugin-support for various java frameworks like RESTful webservice frameworks, JSF2.x, Primefaces3.x, SpringMVC, Struts but you may not sure to use the same version of framework. Some plugins may not work sufficient according to your business needs. Even if you okay with existing version it is not very friendly to develop Rich real-time UI development because Netbeans with Primefaces, instead you need to manually create XHTML templates.
Netbeans comes with nice support for Glassfish and tomcat, (other servers I am not sure but support is in-built). You can remote deployment with ease. Netbeans learning tutorials on JavaEE nice for beginners in the subject.
Netbeans also available as zipped bundle, hence no need to install even on Windows machines.
Eclipse has got better support with Java RoboCode learning tool (initiated by developed by IBM long ago.).
Also Netbeans comes with nice support for HTML5, Groovy, PHP, C++ as well (according to posts by users community, because I did not use them).
For the last few years, we've used m2eclipse without issue, however it seems that the "new" version (ie. m2e) has broken backwards compatibility - something that I really hope that I've just misinterpreted.
My problem is this: I'd like to be able to build my existing project with the minimal amount of fuss. I don't have the time to write connectors for the 3 plugins that don't have them - my understanding of 2 of them is quite limited in the first place, and I have no understanding of the Eclipse plugin mechanism - but I'd still like to be able to use Eclipse to build the project.
Can I achieve this without reverting back to the old (working) version m2eclipse?
Am I correct in my understanding that there is no way to upgrade without having a connector for each plugin?
It seems as if my understanding was correct if this blog post is anything to go by:
http://grumpyapache.blogspot.com.au/2011/08/mess-that-is-m2e-connectors.html
M2E can invoke a plugin as part of the automatic build process if, and only if, there is a connector for the plugin, or you specially configure the plugin
... which means that:
You can no longer use your own plugins in the Eclipse automatic builds, unless you create a connector for the plugin, or create a project-specific configuration
The post goes on to list the issues with this approach. These are many of the same issues I have with the approach.
RANT: So there you have it - the m2e approach does suck as much as I feared it did! I was beginning to think it was just me!
Usually when one wants to create a new file in the Eclipse IDE , Java, Javascript, Colsdfusion PHP etc are provided as the options for the new files.
I recently downloaded Eclipse for Coldfusion 8 and excecuted the file "software/dw/java/europa/J2EE-SDK-Europa-33-win32.zip" .
Now when I want to create a New File "only JAVA " option is available. There is no coldfusion or HTML!
So can any one provide me the Exact/correct link for Codfusion related Eclipse?
(On the Eclipse website there are many Eclipse related downloads but I am not sure which one is specific for Coldfusion.)
There's CFEclipse, a free, open-source Eclipse plug-in for working with CFML. And of course there's Adobe's ColdFusion Builder, a commercial product that works as either a plug-in for an existing Eclipse installation, or as a full stand-alone product (with Eclipse already baked in).
CFEclipse 1.3.6, the current stable version, works with Eclipse 3.4.x or 3.5.x. Here's the CFEclipse wiki.
The stated Eclipse versions required for ColdFusion Builder are 3.4.2 or 3.5. Here's Adobe's requirements page.
If you're using one of these as a plug-in and you don't need a lot of the other Eclipse features, the J2EE version of Eclipse is probably overkill (it's the biggest package). You can try out a more minimal Eclipse install, then update and add plug-ins as you need them. Try the Eclipse Platform Binary, for example.
There's also Adobe's ColdFusion Builder IDE specially created for this purpose. It proposes some features not available in CFEclipse, but not free (though there's a trial version available).
In addition to Ken's answer please note that you can already use preview builds of CFEclipse with latest Eclipse 3.6 Helios. I am using this configuration on daily basis and it is pretty stable and more efficient than previous version for me.
If you will expierience problems with preview builds, feel free to post them into the CFEclipse groups, developers usually react pretty quickly.
One more hint for you. Sometimes after installing the plugin via Add Sofware further updates do not work correcly. I've experienced this issue few times so it can be useful to know the solution.
To fix this check the Preferences > Install/Update > Available Software Sites. If needed entry missing -- create it manually using the same update URL as for installation.
Also there's an Eclipse-based version of Adobe CF manual available, see this help page for details.
Hope this helps.
I have just seen that new major release (3.6 Helios) of eclipse is available for download. I want to try it, but before that I want to know if anybody experienced any major problems.
I want to determine If I could try this or not, since my project setup is complex and easily takes 2, 3 hours normally; I don't want to take any risk.
No major issue sp far.
The main problems I have seen are platform specific, like this crash in Ubuntu.
Small differences are noted in this blog post.
As usual, I always prefer a full Eclipse installation beside the ones I already have.
And for major update, I like to recreate a workspace dedicated for that release, just to be on the safe side.
That way, my old Eclipse release still has its own workspace fully functional.
I also test the plugins in both version by using a shared dropins folder.
Yes i experienced a major problem with helios, but only in WTP context. If you work with WTP you should immediately update to WTP-M-3.2.1. This should fix the issue of taking up to a minute for hot deployment (re-publishing to the server). The eclipse bug issue.
The most disturbing thing for me was the way j2ee projects are configured: there is no more j2ee dependencies, and it is not obvious at the first glance to see you have to use resource assembly (but it does not resist a few minutes searching the web).
Apart for that, I had no real issue in updating: everything went smooth, and plugins I use work well under helios.
Nothing so major, but some suggestion features are a bit buggy:
sometimes instead of suggesting to create a method, it suggest a cast, and inserts a cast to Object
when there are interfaces methods with generics, some of them are added as unimplemented even though they exist in the parent class.
These are two things I encountered for the past week.
On Windows, Helios does appears to have a pretty critical conflict with the latest oracle JDK patch (JDK 1.6 update 21):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=319514
Any version before that is ok.
There is an issue with Helios and Oracle JVM 1.6.0 update 21. Eclipse launcher sets permgen size using Sun-jvm-specific command line option, but Oracle changed vendor string from "Sun Microsystems" to "Oracle", and Eclipse now fails to detect Sun-JVM, so it is not setting right permgen size. Quick solution is to set permgen by yourself in eclipse.ini.
I'm getting incredibly slow autocomplete. The bug , with a workaround, is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=317979
We switch to 64bits Helios under Windows 7 recently. We saw a major improvement in memory management no more Out Of Memory errors inside Eclipse. Much better performances as well. But we have a big issue with SVN and SVN Kit plugins they are constantly displaying Malformed Network data errors or Handshake fail errors when synchronising with our repository under svn+ssh. Was perfectly running under 32 bits Indigo or Galileo.