chore(deps): track jcifs 3.0.4-SNAPSHOT for the 15.9 line - #81
Merged
Merged
Conversation
jcifs was pinned to the released 3.0.3 by #68, which was the 15.8 release pin. The 15.9 line moved on in #72 and the CodeLibs libraries were only partly bumped back to development snapshots afterwards, in #75 and #76, so jcifs stayed on the 15.8 release while its repository develops 3.0.4. That matters now: 3.0.4 carries the configuration property fixes from codelibs/jcifs#81, including the warning that tells an operator when a property is being ignored because it still uses a pre-3.0.0 prefix. codelibs/fess#3433 and codelibs/fess-crawler#205 correct Fess's own uses of those names, and this is the dependency that makes the diagnostic reach anyone whose configuration still has them. 3.0.4-SNAPSHOT resolves from the Central Portal snapshot repository this pom already declares.
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.
Why
jcifs.versionwas still3.0.3, a 15.8-line release pin, while the repositorydevelops
3.0.4-SNAPSHOT.#68("pin dependency versions to released artifacts") pinned fesen-httpclient,corelib, curl4j, java-saml, jcifs, nekohtml and spnego for the 15.8 release.
#72thenmoved this pom to
15.9.0-SNAPSHOT, but the usual counterpart — the"bump CodeLibs libraries to next development snapshots" step,
#58in the previouscycle — only ever ran partially:
#75moved sai and#76moved fesen-httpclient.jcifs and five others were left on their 15.8 releases.
It matters for jcifs specifically right now. 3.0.4 carries the configuration property
fixes from codelibs/jcifs#81 — the documented property names were wrong across the
whole repository, and a pre-3.0.0 key is silently ignored rather than reported.
codelibs/jcifs#87 corrects the names and makes
PropertyConfigurationwarn when itis handed a key under an obsolete prefix, naming the replacement.
codelibs/fess#3433 and codelibs/fess-crawler#205 fix Fess's own uses of those dead
names; this bump is what makes the diagnostic reach users whose own configuration still
carries them.
Resolution
3.0.4-SNAPSHOTresolves from thecentral-portal-snapshotsrepository this pomalready declares (
snapshotsenabled,updatePolicyalways):Note the snapshot currently published (
20260910.113011, build 3) predates the mergeof codelibs/jcifs#87 by about half an hour, so the fixes land with the next snapshot
deploy rather than immediately. The coordinate resolves either way, so nothing is
broken in the meantime.
Not in this PR
The same drift left five more CodeLibs libraries on their 15.8 release pins while their
repositories develop the next version:
corelib.versioncurl4j.versionjava.saml.versionjhighlight.versionnekohtml.versionspnego.versionEach of those pulls in whatever else has landed upstream, which is a separate call from
this one, so I left them. Happy to do the sweep in a follow-up if you want the 15.9 line
back on snapshots across the board.