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
The app dependencies in rebar.config and .app.src are not in sync with the actual usage in the application.
This is currently one of the blockers for using the application as a dependency in your own project - at least if you want to use relx and rely on proper OTP rules for releases.
E.g., in riak_ee all the non-OTP applications show up without a version number in the directory name in the lib directory.
This complicates release upgrades a lot.
The fix is to simply bring the files in sync with reality.
The problem and the fix applies to all versions of the application, not just the one listed in the Fix and Affected Version(s) fields.
[Created in JIRA by Torben Hoffmann]
The text was updated successfully, but these errors were encountered:
We'll take a look at the PR and get it merged post-2.1.2 - I realize it may be a small change, but we're trying not to pull anything new into 2.1.2 if it's not necessary for the release at this time.
The app dependencies in rebar.config and .app.src are not in sync with the actual usage in the application.
This is currently one of the blockers for using the application as a dependency in your own project - at least if you want to use relx and rely on proper OTP rules for releases.
E.g., in riak_ee all the non-OTP applications show up without a version number in the directory name in the lib directory.
This complicates release upgrades a lot.
The fix is to simply bring the files in sync with reality.
The problem and the fix applies to all versions of the application, not just the one listed in the Fix and Affected Version(s) fields.
[Created in JIRA by Torben Hoffmann]
The text was updated successfully, but these errors were encountered: