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
In WSO2 Micro Integrator (MI), managing and sharing artifacts such as connectors, and libraries is currently a cumbersome and manual process.
Describe your problem(s)
No response
Describe your solution(s)
The proposed solution involves integrating a Nexus server for managing WSO2 MI connectors as Maven artifacts. The first step is setting up or using an existing Nexus server to store connectors in ZIP format, with automated uploads from GitHub via GitHub Actions, ensuring proper versioning and publishing. Additionally, the connector store’s JSON file will be dynamically updated by retrieving metadata from Nexus each time a new connector is uploaded. The WSO2 MI VS Code plugin will be enhanced to treat connectors as Maven dependencies, automatically fetching the connector ZIP files and dependent JARs from Nexus, with the POM file updated to manage these dependencies. Finally, comprehensive testing will ensure connectors are uploaded, retrieved, and integrated correctly, with updated documentation to guide users on adding connectors via the VS Code plugin.
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered:
rosensilva
changed the title
[New Feature]: Centralized Artifact Exchange and Dependency Management for WSO2 MI
[New Feature]: Centralized Dependency Management for WSO2 MI Connectors and Connector Dependencies
Sep 5, 2024
Description
In WSO2 Micro Integrator (MI), managing and sharing artifacts such as connectors, and libraries is currently a cumbersome and manual process.
Describe your problem(s)
No response
Describe your solution(s)
The proposed solution involves integrating a Nexus server for managing WSO2 MI connectors as Maven artifacts. The first step is setting up or using an existing Nexus server to store connectors in ZIP format, with automated uploads from GitHub via GitHub Actions, ensuring proper versioning and publishing. Additionally, the connector store’s JSON file will be dynamically updated by retrieving metadata from Nexus each time a new connector is uploaded. The WSO2 MI VS Code plugin will be enhanced to treat connectors as Maven dependencies, automatically fetching the connector ZIP files and dependent JARs from Nexus, with the POM file updated to manage these dependencies. Finally, comprehensive testing will ensure connectors are uploaded, retrieved, and integrated correctly, with updated documentation to guide users on adding connectors via the VS Code plugin.
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: