[WFCORE-7544] Fix usability issue renaming installation-manager.sh to…#6706
[WFCORE-7544] Fix usability issue renaming installation-manager.sh to…#6706yersan wants to merge 1 commit into
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
… ./installation/_installation-manager_helper.sh Jira issue: https://redhat.atlassian.net/browse/WFCORE-7544 Signed-off-by: Yeray Borges <yborgess@redhat.com>
| <!-- Unstable API Annotation Index --> | ||
| <package name="org.wildfly._internal.unstable-api-annotation-index" optional="true" valid-for-stability="preview" /> | ||
| <package name="org.wildfly.unstable.annotation.api.indexer" optional="true" valid-for-stability="preview" /> | ||
| <package name=".installation"/> |
There was a problem hiding this comment.
@jfdenise We are adding this new .installation directory under the standard galleon content directory, so I understand there is an auto discovery done by Galleon and a new package, named ".installation" is created out of the box.
My question is more about design than functionality. Under which circumstances should we count on this auto discovery of package names instead of creating our own dedicated package name?
I only can think of having a maybe better package name, but I am not sure
|
Core -> Full Integration (with SecurityManager) Build 15454 outcome was FAILURE using a merge of 7f9fdca Failed tests |
|
Core -> Full Integration Build 15128 outcome was FAILURE using a merge of 7f9fdca Failed tests |
|
Core -> WildFly Preview Integration Build 132 outcome was FAILURE using a merge of 7f9fdca Failed tests |
|
Core -> Full Integration (with SecurityManager) Build 131 outcome was FAILURE using a merge of 7f9fdca Failed tests |
… _installation-manager_helper.sh
Jira issue: https://redhat.atlassian.net/browse/WFCORE-7544