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
Hardcoding the DDF version for the feature repos (https://github.com/connexta/admin-console/blob/master/features/admin-query/src/main/feature/feature.xml#L20) causes downstream projects to start that version of features in addition to starting DDF features for the version that the downstream project points to. Effectively, the system ends up starting duplicate DDF features, some for the version that admin-console points to and some for the version that the downstream project points to.
This can be fixed by changing the feature repos to use a version range instead. However, there is a current bug in Karaf that breaks this use-case: https://issues.apache.org/jira/browse/KARAF-6294. Once this bug is fixed, we should use version ranges for the feature repos.
The text was updated successfully, but these errors were encountered:
brjeter
added a commit
to brjeter/admin-console
that referenced
this issue
Jun 11, 2019
Hardcoding the DDF version for the feature repos (https://github.com/connexta/admin-console/blob/master/features/admin-query/src/main/feature/feature.xml#L20) causes downstream projects to start that version of features in addition to starting DDF features for the version that the downstream project points to. Effectively, the system ends up starting duplicate DDF features, some for the version that admin-console points to and some for the version that the downstream project points to.
This can be fixed by changing the feature repos to use a version range instead. However, there is a current bug in Karaf that breaks this use-case: https://issues.apache.org/jira/browse/KARAF-6294. Once this bug is fixed, we should use version ranges for the feature repos.
The text was updated successfully, but these errors were encountered: