You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We recently updated ORT for the v3 license workflows to support cargo and pnpm usage in the zowe vscode exporer component. ORT was previously kept down-level to avoid issues with Java 17 ORT clashing or not scanning APIML Java 8 projects correctly. We need to investigate if this clash is still happening, and if it is, plan how to address this for v2. Ideally we want to scan with the newer version of ORT, but if that approach isn't feasible, the answer may as simple as a separate docker container w/ a different release tag which contains down-level ORT.
The text was updated successfully, but these errors were encountered:
We recently updated ORT for the v3 license workflows to support cargo and pnpm usage in the zowe vscode exporer component. ORT was previously kept down-level to avoid issues with Java 17 ORT clashing or not scanning APIML Java 8 projects correctly. We need to investigate if this clash is still happening, and if it is, plan how to address this for v2. Ideally we want to scan with the newer version of ORT, but if that approach isn't feasible, the answer may as simple as a separate docker container w/ a different release tag which contains down-level ORT.
The text was updated successfully, but these errors were encountered: