Remove default plugins #70
Merged
Conversation
This file contains hidden or 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
Default plugins should be installed only using the blueprint mechanism from the ecosystem. With the old list of default plugins, this was not really usable, because the old list of default plugins always installed nearly all plugins available, so that the user had no way to create a smaller default set. So with this, we completely remove the default plugin list. All necessary plugins like the legacy plugins for CAS will still be installed by the dependency checks.
pfeuffer
force-pushed
the
feature/remove_default_plugins
branch
from
30b009d to
4ac29b3
Compare
pfeuffer
added a commit
that referenced
this pull request
Jun 28, 2023
Default plugins should be installed only using the blueprint mechanism from the ecosystem. With the old list of default plugins, this was not really usable, because the old list of default plugins always installed nearly all plugins available, so that the user had no way to create a smaller default set. So with this, we completely remove the default plugin list. All necessary plugins like the legacy plugins for CAS will still be installed by the dependency checks.
eheimbuch
pushed a commit
that referenced
this pull request
Jul 24, 2023
Default plugins should be installed only using the blueprint mechanism from the ecosystem. With the old list of default plugins, this was not really usable, because the old list of default plugins always installed nearly all plugins available, so that the user had no way to create a smaller default set. So with this, we completely remove the default plugin list. All necessary plugins like the legacy plugins for CAS will still be installed by the dependency checks.
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.
Default plugins should be installed only using
the blueprint mechanism from the ecosystem. With
the old list of default plugins, this was not
really usable, because the old list of default
plugins always installed nearly all plugins
available, so that the user had no way to create
a smaller default set.
So with this, we completely remove the default
plugin list. All necessary plugins like the
legacy plugins for CAS will still be installed by
the dependency checks.