My project was created several years ago, and it's use babel 6.x.
Now, I need to import a plugin that depend on babel 7.x , and I try to use it, and didn't find problems yet, but I know it's a dangerous action to keep two different mainly babel version in one project.
And it will make a big influence if I upgrade the babel version from 6.x to 7.x, I guess I have no time to do it. So can I both use babel 6 and 7 in my project, and can anyone told me the risk of it?
Related
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 :)
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 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
Within the context of upgrading plugins explain how to resolve plugin dependencies when NetBeans user interface's reports specific missing dependencies, yet these do not resolve with a google search or are unmentioned in the netbeans FAQ.
The practical example leading me to ask this question was when I attempted to install an in-development-plugin org-netbeans-modules-htmlprojects.nbm. It requires General Queries API v1.24 and I have v1.19.1.
Have a look at the bug report that mentions the nbm, it's for version 7. This also means that the mentioned version for GQA is also version 7 specific.
You best choice is probably to upgrade to version 7, it has some nice improvements over version 6.9 like HTML5 support. As a new install picks up the configuration of an installed previous version upgrading shouldn't be a lot of work.
EDIT based on restated question:
The short form: you cannot, it's not meant to work that way.
The long form: due to what happened here and the inner workings of Netbeans the error message was less clear than it could have been...
you downloaded a module for a higher version than the installed one
Netbeans' nbm deployment descriptor states dependencies on editor modules, not on editor versions - see inside the nbm which is actually a ZIP file Info/info.xml, manifest element, OpenIDE-Module-Module-Dependencies attribute.
Normally that error would not happen, as the version of the nbm will normally match the editor version, and the dependencies should either be satisfied or satisfiable by on-the-fly installation of the missing dependencies.
I've recently learned that the import section from feature.xml is legacy, and the actual dependency work is delegated to the p2 engine, which uses the information from the plugin manifest.
I am not sure though if p2 is available for all recent versions of Eclipse, or in all Eclipse-based products, so I'm not sure if it is safe to remove the import section from feature.xml.
Under what circumstances is it safe to remove the import section from feature.xml? Assume that we are taking into consideration Eclipse 3.4 or newer.
P2 was introduced in Eclipse 3.4 release. It had quite a few issues in that release, so a way was given to revert your Eclipse install to using the legacy Update Manager. Starting with 3.5 release, p2 is quite stable and is a definite improvement over the old Update Manager. I am not certain if it is possible to revert to the Update Manager in 3.5 or higher release. I certainly haven't heard of anyone doing this.
P2 is present in all Eclipse packages starting with 3.4 release.
I wouldn't categorize feature import as a deprecated feature. You would still want to use it to pull in plugins when you don't have direct OSGi dependency on them.
Consider the case where you are building an extension to JDT. Say you only depend on JDT core api (no UI extensions). If you only rely on OSGi dependencies, when your plugin is installed, p2 will dutifully install JDT core bundle, but not the UI bundle. Perfectly fine from OSGi perspective, but probably not what you intended.
I recommend sticking with feature import to describe your high level dependencies to make sure that they are installed in full. Relying only on OSGi dependencies works best for free-floating bundles that aren't part of something bigger that should be installed as a unit.