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
At xxx project structure we organized the logic as
Integration logic is deployed separately
Endpoints, properties and other environment dependent things that are used by integrations are deployed separately (env dependent CApp)
When multiple people work on endpoint project adding their own endpoint, the artifact.xml and pom.xml files get conflicted. The reason we identified was, the integration studio try to reorganize the entries in these files in alphabetical order or some manner automatically. When merging the pull requests, even if developers are not supposed to know or touch artifact.xml most of the time it is conflicted by changes of another developer who added a completely different endpoint.
This makes the integration studio not suitable for team development. Please fix.
Description
Description
At xxx project structure we organized the logic as
When multiple people work on endpoint project adding their own endpoint, the
artifact.xml
andpom.xml
files get conflicted. The reason we identified was, the integration studio try to reorganize the entries in these files in alphabetical order or some manner automatically. When merging the pull requests, even if developers are not supposed to know or touchartifact.xml
most of the time it is conflicted by changes of another developer who added a completely different endpoint.This makes the integration studio not suitable for team development. Please fix.
Affected Component
IntegrationStudio
Version
MI 4.2.0
Environment Details (with versions)
Windows 10
Related Issues
https://github.com/wso2-enterprise/wso2-mi-internal/issues/660
The text was updated successfully, but these errors were encountered: