-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alfredops 856 #158
base: master
Are you sure you want to change the base?
Alfredops 856 #158
Conversation
…able on remote repo's. updated docker plugin
@@ -1,5 +1,5 @@ | |||
plugins { | |||
id 'eu.xenit.docker-compose' version '5.3.2' apply false | |||
id 'eu.xenit.docker-compose' version '5.5.0' apply false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
docker-compose files have to be upgrade to V3.x
version: '3.2' (Found in docker.yml files). This comment can be ignored.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgrade for docker-compose V5.3.2 -> V5.5.0
Fixing the community version numbers.
@@ -1,5 +1,5 @@ | |||
ext { | |||
alfrescoBaseWarBom = 'org.alfresco:acs-community-packaging:6.2.1-A7' | |||
alfrescoBaseWarBom = 'org.alfresco:acs-community-packaging:6.3.0-repo-4735-2-15' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a weird version that can potentially be removed in future?
Updated Readme.md to prevent a configuration bug that causes log4j2 logging to fail