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 need to figure out a way (if there is any) how to deal with external dependencies required by both AE node and application on top of AE plugin, on different versions.
Example case - Cowboy.
AE node uses it for HTTP API endpoints. AE_MDW uses it, via Phoenix.
Using the same version would mean, we would have to use old version of Phoenix, where it's Cowboy dependency version matches the one used in AE node.
It's now unclear how to do this sensibly, or if it's possible to do it at all, considering that AE node and application on top of AE plugin need to share the same path to libraries.
The text was updated successfully, but these errors were encountered:
We need to figure out a way (if there is any) how to deal with external dependencies required by both AE node and application on top of AE plugin, on different versions.
Example case - Cowboy.
AE node uses it for HTTP API endpoints. AE_MDW uses it, via Phoenix.
Using the same version would mean, we would have to use old version of Phoenix, where it's Cowboy dependency version matches the one used in AE node.
It's now unclear how to do this sensibly, or if it's possible to do it at all, considering that AE node and application on top of AE plugin need to share the same path to libraries.
The text was updated successfully, but these errors were encountered: