Fix incorrect info in meta.json#270
Open
ochnios wants to merge 1 commit intowso2-extensions:masterfrom
Open
Conversation
1de1a61 to
8ed17b3
Compare
Contributor
|
Are you using VSCode extension for development? If possible, please share the reproducing steps. |
Author
|
@arunans23 we use VS Code for some of our integrations but not for all ones. I tried to add the file connector using VS Code extension and run integration - it actually worked. However, I noticed that missing commons-vfs library has been attached to CAR file itself along with connector: But it doesn't work when I use a standalone connector zip file downloaded from official Github release or WSO2 store and deploy in old school way to |
Author
|
I think this may be related to this issue: wso2/product-micro-integrator#4498 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Purpose
The current
meta.jsonstates thatesb-connector-filev6.0.0 is compatible with Micro Integrator (MI) 4.5.0 and 4.4.0. This is not accurate due to an underlyingcommons-vfs2library incompatibility.wso2-synapse:4.0.0-wso2v268) providescommons-vfs:2.2.0-wso2v22.esb-connector-filev6.0.0 requires a newer version (2.10.0-wso2v4) of thecommons-vfs2library.Attempting to deploy
esb-connector-filev6.0.0 on MI 4.5.0 results in a runtime exception, as the older VFS library provided by MI is loaded and is not compatible with the connector's requirements.Since repository issues are disabled, this PR is being used to highlight this incompatibility and correct the
meta.json.Goals
The goal of this PR is to update the connector's compatibility information in
meta.jsonThis change removes the inaccurate claim that connector v6.0.0 is compatible with MI 4.5.0 and 4.4.0, which will prevent other users from encountering this deployment failure.
Approach
This PR directly modifies
meta.jsonto remove the incorrect compatibility entry for MI 4.5.0 and MI 4.4.0Suggested solution:
For a permanent fix, you could consider one of two options:
commons-vfs2library.commons-vfs2dependency within the connector to be compatible with the2.2.0-wso2v22version provided by MI.Attachments
Exception log