On client machines that were working fine yesterday we get the following error message:
The license isn't compatible with the current product version (6.x). The license can be used only with product versions released before 05/05/2016. Current product version was released on 05/05/2016.
We are using Version 6.0.2 and coincidentally our support ran out today.
Any ideas on what we need to do?
I'm sorry that you see this issue. The license is valid for all JxBrowser 6.x versions, but several months ago we discovered that the license checking mechanism has issue with parsing the support expiration date. We fixed this issue right away in JxBrowser 6.1. I confirm that JxBrowser 6.0.2 has this issue. To fix it I recommend that you upgrade to JxBrowser 6.1 or higher.
Related
is there a way to know when a version of Flyway is going to get deprecated?, actually we were using 6.0.7 the last year and then got deprecated like 6 months ago, now we are using 6.4.1 but I tried to find something on the blog and documentation but there's nothing about some news of when a version is going to be deprecated, only when we run our java spring boot project we know that a version is not usable. And we're aware of this because there's a lot of changes in version 7+ that doesn't work with our project (tested version 7.0.1 and the app crashed) and we need to estimate the cost of the changes.
Any help would be appreciate, thanks.
Flyway releases via Maven OSS. Old versions are kept indefinitely and are outside of Redgate's control. In theory, all older versions which are currently available on Maven will continue to be available for all time.
Newer versions may deprecate features over time, but older versions will always be available.
Yesterday I was wondering why http://download.qt.io/archive/qt/5.5/5.5.1/ was giving a 404. Then I checked about 10 mirrors for it - and they also were all 404?
So I thought just their server is down or something (why would mirrors be affected?). But now today, http://download.qt.io/archive/qt/5.5/5.5.1/ still does not exist, yet some really old versions (1.x) and other versions (5.1 and 5.9 for example) exist at http://download.qt.io/archive/qt/
I haven't seen any announcements about Qt deprecating version 5.5. Has it been taken down permanently?
It's now under http://download.qt.io/new_archive/qt/ which is not mirrored - it was done due to some mirrors had problems hosting all Qt versions.
When I scan my site with modern.ie, it says:
We've found frameworks or libraries that are not up-to-date and might
contain bugs.
modern.ie detects that my site is running jQuery 2.2.0 (the latest version).
Is there a bug with the modern.ie site?
What version of jQuery are you using?
You can check the current open bugs in its public GitHub repo https://github.com/MicrosoftEdge/static-code-scan and open a new issue if you find one
When I try to add a web-service-client from a WSDL, I get an error, and to get past this error I have to delete a file called "javax.xml.soap_1.3.0.v201105210645" from the 'plugins' folder.
Here's an original post:
http://forum.spring.io/forum/spring-projects/springsource-tool-suite/91609-sts-2-5-1-java-io-filenotfoundexception-lib-saaj-jar
Isn't there a way to fix this permanently?
I tried this again with the latest STS 3.6.3 version and it seems to work just fine. The Eclipse bug at https://bugs.eclipse.org/bugs/show_bug.cgi?id=364026 is fixed since quite some time. Please make sure you are using STS on top of the latest Eclipse 4.4 release. The bug in Eclipse Webtools got fixed for Eclipse Luna (4.2), so if you are running STS 3.6.3 on an older Eclipse version, this bug is still there, I would guess. Hope this helps!
We are running an old version of plone (Version 2.0.5). (We will migrate next year to plone 4)
I was trying to install the Plone Hotfix 20121106, but (as mentionened in the installing description), the hotfix will not apply to the version 2.0.5 of plone.
Questions:
Are the security vulnerabilites also relevant for the plone version 2.0.5?
Is there another way to install the hot fix on that old version of plone?
Some of the security vulnerabilities do apply to 2.0.5, yes.
However, there are other unpatched vulnerabilities in 2.0.5 not addressed by this hotfix, and you want to move away from this old a version as soon as possible. The Plone security team does not provide official support for Plone versions this old; currently 3.x and 4.x releases are supported.
You can unzip the hotfix into your Products folder, and it should just work. I believe people have tested it on 2.0.x installations already; the test coverage certainly was run on 2.1. You'll have to run your own tests though to make sure nothing (important) breaks for you when the fix is installed.