Allow adding custom external jars to classpath #2726
Draft
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.
This is a draft showing the described changes to allow adding external jars to the classpath. I'm happy to add this functionality to the remaining images if you agree.
Description
Adds a new environment variable
SE_EXTRA_LIBS
which allows to add custom external jars to the classpath.Motivation and Context
Selenium makes it possible to customize a node. While this works pretty well when running a node as shown in the documentation, it is not possible to achieve the same using the Docker images. Right now
--node-implementation
can be passed to thestart-*.sh
script usingSE_OPTS
, but there is no way to pass--ext
to it.Introducing a new environment variable representing
--ext
namedSE_EXTRA_LIBS
would allow to extend the classpath in a simple way. The desired jars could then be added to the Docker container in the user's preferred way:This mechanism can be applied in the same way to all images.
Types of changes
Checklist