I am currently working on a code which has Javascript library Jquery Migrate which currently uses version 1.4.1. Can someone guide me how can I update the Jquery Migrate library to version 3.4.0 ?
Use something like this npm i jquery-migrate#3.4.0. You can replace the 3.4.0 with every version you'd liked.
Related
We used to have GWT 2.4 & GXT 2.2.5 and we are migrating to GWT 2.8.1.
Now I am using GWT 2.8 with gxt 2.2.5 and Jdk 1.8.0_291, even when upgrading gxt-2.3.1a-gwt22 I still get this error when maven is building I got this error
jar:file:/war/WEB-INF/lib/gxt-2.3.1a-gwt22.jar!/com/extjs/gxt/ui/client/widget/form/ListField.java' > Line 322: The method append(boolean) is ambiguous for the type StringBuffer
After searching I thought it is imposible to resolve it, I don't have the right to edit the dependency.
So I decided to upgrade gxt to 4.0.2, am I right?
but when I did all the app broke, most of Types don't exist anymore and the migration is not well documented on sencha website, they provide a unique page that doesn't help.
Do you have a tutorial or a guide that helps? or maybe a workaround?
Moving from GXT 2.x to 4.0.2 will create a lot of work. Take a look here:
Sencha GXT 2.x to 4.x Migration Guide
To get gxt-2.3.1a working with GWT 2.8.2 or even 2.9.0 (and maybe 2.10.0 - did not check this) you need to fix the bugs. The easiest way would be to
override the class and correct the things that are wrong.
F.e.: Fixing the ListField bug, you have to:
create a package: 'com.extjs.gxt.ui.client.widget.form'
create a class named 'ListField'
copy the code from the ListField class into you new class
fix the problem
I did that in the past and IIRC it was not much work.
I am trying to implement SOAP services in my app, the best plugin I found is CXF, but I couln't install it, it looks like that I should put some additional repository.
I raised an issue in the source page, but if someone has faced this before, can share the solution plz?
If you are trying to use version 3.1.2 of the plugin, you want org.grails.plugins:cxf:3.1.2, not org.grails.plugins:grails-cxf:3.1.2.
The problem is that the plugin's documentation talks about to use the version 3.1.2, but the latest version in the repository is the 3.0.9
I was using BIRT together with java 1.6 but recently have updated java to the latest version which is a prerequistie for other applications. Since then BIRT is not working.
I was using BIRT 4.4.0.v201405191524.
Is there any possibilty to work BIRT with the java 1.8 version?
BIRT has some dependencies which are given here.
They have specifically mentioned only Java 1.6 JDK/JRE as a pre-requisite but not higher version of JDK/JRE.
The BIRT engine 4.5 itself is still compiled with a java 6 compliance but many eclipse libraries require java 1.7.
I'm using BIRT 4.3.2 v20140211-1400 with java 1.8.
I'm using jre 1.8.20 and compiler version 1.8.
We recently upgraded our Dev environments to use BIRT 4.6.0 v20160607-2122 with Java 8_121, using Eclipse Neon 4.6.2
All is well, BIRT works great, with one minor issue: on the Edit Chart dialog's Select Data tab, the Summation button for the Value Series / Slice Size Definition is always disabled.
I'm following Building a RESTful Web Service -- and was wondering why the gradle wrapper version was 1.11 instead of 2.3? I tried 2.3 and it worked.
Is there a downside to using 2.3 instead of the suggested 1.11?
Most probably the reason is, that at the time of the creation of the tutorial the stable Gradle version was 1.11, and the tutorial just wasn't updated since then. Usually there is no downside to use a newer version, except if there are some features used, which are now deprecated or removed in a newer version.
We have a project where we're using Spring-js. With it comes Spring-dojo and the full dojo package. But in the current version of Spring-js (2.0.9), it's using dojo 1.3. Is there a way to upgrade manually to dojo 1.4? Or even a new Spring-js.jar-file that can be donwloaded that uses dojo 1.4?
Yes. If you are using the ResourceServlet, you can simply drop the new version of Dojo in the top-level directory of your WAR structure. The ResourceServlet always looks there before it looks on the classpath, thus resources in top-level of the WAR take precedence. I would suggest using a full uncompressed source distro of Dojo during development, and then doing a custom build that is tailored to your usage patterns for production.
Beware that we've occasionally seen some minor incompatibilities when upgrading Dojo versions, so be on the lookout for that and report any issues in the Web Flow Jira.
I suspect we'll be upgrading to Dojo 1.4 in the official distribution for the upcoming Spring Web Flow 2.1 release.
Btw., spring webflow 2.0.9 uses dojo 1.2.4 not 1.3 as the release notes tell