I'm using Apache poi 1.3.1 library in many database for xpages export/import actions. when I upgrade notes 10 to 11 and notes 11 give me a library errors.
Since I see that the library is installed but the compiler doesn't resolve the bundle, I expect that it's the Target Platform bug described here, with the workaround being to add the data/workspace/applications/eclipse directory to your TP: https://frostillic.us/blog/posts/2018/10/19/058650e080e352178525832b00519d2c . That recurs frequently during any upgrade involving 9.0.1FP10 through to current versions.
Related
We upgraded our Oracle DB and oracle client from 12.1 to 19.10.
Our application server have below setup
OS is Linux
Python version is 2.7.5 and there is no plan to upgrade the python version yet
cx_Oracle library version is 5.3
A quick test shows the application works fine but I am wondering if I need to upgrade the cx_Oracle library? Does it have a support expiry date? I tried to google it, read the information on its Github page but can't find any statement that answers my question.
This combination hasn't been tested. But since the Oracle Client libraries keep compatibility it is likely to work, subject to whatever underlaying enforced changes have been made to the Oracle libraries, perhaps to drop unsupported TLS versions or whatever has occurred in the 8 years since 12.1 was released that I don't know about. You application testing should be the final confirmation.
You should definitely set a goal to update to Python 3 so you can get the latest cx_Oracle version.
I upgraded my Domino 9.0.1 to 10 after my databases (used POI import/Export) give POI libraries errors. I'm using Eclipse Update Site database for loading POI. I tested po
cant load POI libraries:
import java lib are not load
Domino console POI services status:
Your Target Platform setting in Designer may have been messed up by the V10 upgrade - it's a very-common issue with 9.0.1FP10 and V10. "Fix #1" here may be what you need: https://frostillic.us/blog/posts/058650E080E352178525832B00519D2C
Welcome to Stack Overflow. The first image shows build errors in Domino Designer. Did you upgrade your Designer to 10 too? If so, then you should reinstall the POI libraries in Designer from your update site.
We have SAP Hybris Commerce version 5.1.1 with custom extensions installed. Now we need to upgrade it to newest version 6.2.
My question is: Can we upgrade it to 6.2 and skip all versions between 5.1 and 6.2? Or must it be done by upgrading to 5.2, then to 5.3 and so on?
Yep - 5.1.1 to 6.2 ought to work (I've been working on a project that's done exactly this).
You will probably have to make some changes - watch out for any customisations you've made - it might be worth reading through the release docs to have an idea of what's changed - off the top of my head the structure of add ons is one area that's a bit different between 5.1 and 6.2, but otherwise things should work OK in theory.
Yes you can directly update to 6.2.
It's important to regulary update your hybris version. You should not have so much gap with current version. Indeed it become tougher to migrate your custom code.
Upgrading each minor version in a row is totally useless most of the time. Only do this if you have issues you can't solve while migrating to the target version.
You should take a look at this migration documentation and this guide (it can be used even if it doesn't match your version).
Note that some stuff like promotion are totally different in hybris 6 so you can expect some trouble to migrate everything. Take care of your extensions generated with old template also.
5.5.1 introduces JDK8 and Spring 4, I would not underestimate this change! Depending on the size of your project I would first go for 5.5.1. Also notice the MySQL change for 6.2 (5.6). Don't forget to declare deployment tables in your items.xml. Search for "third-party compatibility" and "release notes" on the wiki. Also try shifting to the backoffice since the hMC is marked as deprecated.
Yes you can migrate directly 6.2.
The time and difficulty depends on your custom code (and how much it respects good practices : naming conventions, usage of service, architecture respect...etc)
You might also consider that HMC is deprecated in 6.2
To convince my employers of the benefits of ANTLR and StringTemplate, I constructed a small demonstration first in Java. But Java is not one of our preferred languages, so I translated it to C#. Using VS2015 (Community Edition) and various instructions on the net I got only so far. I now get
ANTLR cannot generate 'org.antlr.v4.codegen.CSharp_v4_5_2Target' code as of version 4.3
Incompatible versions? Which versions of what libraries are compatible for a successful build. I could not work out how to use GitHub. There didn't seem to be a package to download, and I could not see how to download a set of files to compile.
Update 1
Randomly installing versions of whatever I can find, I have now got it down to loads of errors like this from the generated code.
CS0103 The name '_errHandler' does not exist in the current context
Update 2
I have subsequently tried (and failed) to get it going in VS2010(Express). I think that version is seriously hobbled. I can't get NuGet working on it. I am now going to try to install VS2013 as that seems to be the most commonly referred to in this ANTLR context. With VS2015 I have been through all the .NET versions I have installed on my machine back to v3, with no success. It now fails to generate the parsing code.
Update 3 - Solved
Problem solved! Use VS2013 and follow Sam Harwell's clear instructions. Some minor differences between Java and C# to work out when using StringTemplate
My existing project, uses Azure .NET SDK 2.1. I wanted to upgrade the SDK to 2.4, so i dowloaded the latest from here for VS 2012. After successfull installation, when i opened up my solution, the cloud projects did not load. Thats ok, as they have been created using a lower version. So i removed them and created newer cloud projects.
But the thing which astonishes me is, there are many places in the worker role project where its throwing build error as it is not able to find out the assemblies and methods. Is there any easier way to upgrade to sdk 2.4 without making code changes. Which i think is a bad idea to make changes to the stable code, just for SDK upgrade.
When you open a project created using 2.1 SDK and try to open it using 2.4 SDK, you should see the project upgrade dialog which gives you the option to either download 2.1 SDK or convert existing project to target 2.4. Selecting the convert option should upgrade the project to 2.4. Any errors in this process will be reported in the project migration summary report.
If you are not seeing this dialog, then you might still have 2.1 sdk on your machine in addition to 2.4 sdk. In that case, you can go the Azure project properties. That will give you the option to upgrade your project to 2.4.
In regard to the build errors that you are getting for new projects, the error details will help in identifying the root cause.