fix(setup): fail check on a plugin built for another release - #3456
Merged
marevol merged 1 commit intoSep 16, 2026
Merged
Conversation
fess-setup check reported a plugin jar built for another Fess release as WARN,
printed "Usable, with warnings." and exited 0. The upgrade guide says those jars
have to be replaced, and between releases the war changes under a plugin: 15.9
moved the OpenSearch classes into another package and stopped shipping libraries
that 15.8 plugins took from it. Such a jar can keep Fess from starting at all.
Measured with fess-webapp-mcp 15.8.0 left in WEB-INF/plugin of a 15.9 build: the
DI container fails to initialize, every page and API answers 404, and check still
exited 0 with the WARN line.
A plugin for another release is now a FAIL, so check exits 1 and can gate a
deployment as intended, and the line names the remedy:
FAIL plugin fess-webapp-mcp 15.8.0 was built for another release (this Fess
is 15.9; replace it with: fess-setup upgrade plugins)
A snapshot of this release's line, such as 15.9.0-20260914.212412-2, is still OK.
fess-setup upgrade plugins itself was already correct: in the same installation it
replaced the 15.8.0 jar with the 15.9 build and Fess started.
marevol
added a commit
to codelibs/fess-docs
that referenced
this pull request
Sep 16, 2026
…check (#539) codelibs/fess#3456 turns the check line for a plugin jar built for another Fess release from a warning into a failure, because such a jar can keep Fess from starting at all. The check section of install/fess-setup.rst in the 15.9 tree described it as a warning; update the sentence in all seven languages.
marevol
deleted the
fix/setup-check-fails-on-a-plugin-for-another-release
branch
September 17, 2026 13:11
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
fess-setup checkreported a plugin jar built for another Fess release as WARN, printedUsable, with warnings.and exited 0. The upgrade guide says those jars have to be replaced, and between releases the war changes under a plugin: 15.9 moved the OpenSearch classes into another package and stopped shipping libraries that 15.8 plugins took from it. Such a jar can keep Fess from starting at all.Measured with
fess-webapp-mcp15.8.0 left inWEB-INF/pluginof a 15.9 build: the DI container failed to initialize (NoClassDefFoundErroron a nimbus class), every page and API answered 404.checkstill exited 0:Changes
Diagnostics#installedPlugins: a plugin for another release is a FAIL, and the line names the remedy.checkthen exits 1 and can gate a deployment as the command intends:A snapshot of this release's line, such as
15.9.0-20260914.212412-2, is still OK.Verification
test_installedPlugins_failsWhenAPluginIsForAnotherRelease(replacing the WARN test) fails onmainand passes with this change. New:test_installedPlugins_acceptsASnapshotOfThisRelease.DiagnosticsTestandFessSetupTest: 56 tests pass.checkprints the FAIL line above and exits 1.fess-setup upgrade pluginsthen replaced the jar with the 15.9 build and Fess started. It was already correct.checkthen reports the plugin OK and exits 0.The 15.9 documentation describes this check line as a warning; codelibs/fess-docs#539 updates it.