Enforce development environment instructions to Elasticsearch 8.11.3 #7866
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- missing kibana configuration provided by Pierre Mauduit (via geonetwork#6284) - using latest geonetwork image (rather htan 3.99.0) - Setup and document docker folder as independent testing environments
jodygarnett
force-pushed
the
build_docker_elasticsearch_8_guidance
branch
from
d306f24
to
3a90098
Compare
This was referenced Mar 15, 2024
jodygarnett
changed the title
josegar74
reviewed
Mar 18, 2024
| <plugins> | ||
| <plugin> | ||
| <groupId>org.apache.maven.plugins</groupId> | ||
| <artifactId>maven-enforcer-plugin</artifactId> |
There was a problem hiding this comment.
How does this work?
I've tried: mvn enforcer:enforce and get the following error:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce (default-cli) on project gn-es-dashboards: No rules are configured. Use the skip flag if you want to disable execution. -> [Help 1
There was a problem hiding this comment.
Not sure why you are getting that error, it was correctly failing the build if I ran in the wrong version of maven.
There was a problem hiding this comment.
This is used by steps such as compile, for example mvn compile will fail if I set the maven version to one newer than installed on my computer:
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.4.1:enforce (enforce-maven) on project geonetwork:
[ERROR] Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion failed with message:
[ERROR] Detected Maven Version: 3.9.5 is not in the allowed range [4.0.9,).
Accept feedback from review Co-authored-by: Jose García <josegar74@gmail.com>
josegar74
approved these changes
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks for the pointers in the PSC meeting about running Elasticsearch 8.11.3 (as defined in
pom.xml"es.version" file).This PR gathers several outstanding PRs:
docker - missing mentioned kibana configuration #6284
This is for the
dockerfolder which contains development environments for testing.Document use of Elasticsearch 7.6.2 via Apache License 2.0, with a note on license change for 7.11.0 onward #5800
This contained information on license change and troubleshooting information.
Checklist
mainbranch, backports managed with labelREADME.mdfilespom.xmldependency management. Update build documentation with intended library use and library tutorials or documentation