Uses of Package
com.ultikits.ultitools.utils
Packages that use com.ultikits.ultitools.utils
Package
Description
-
Classes in com.ultikits.ultitools.utils used by com.ultikits.ultitoolsClassDescriptionThe files of the module subsystem and the transactions that change them: which folder modules load from, and how
/upm updatereplaces a module's JAR (#505, #513). -
Classes in com.ultikits.ultitools.utils used by com.ultikits.ultitools.commandsClassDescriptionRaised when a module's own unload threw.The uninstall could not delete these JARs now -- the running server holds them open, or the folder is not writable -- and has recorded them, so the next start deletes them before any module loads (#518).The uninstall could not delete these JARs now and could not record their deletion for the next start either (#518).What an uninstall did, and what it could not determine.
-
Classes in com.ultikits.ultitools.utils used by com.ultikits.ultitools.managerClassDescriptionThe subset of a module's
plugin.ymlthis framework needs: its declaredname:andmain:(both nullable - absent when the archive has none or reading failed), itsloadAfter:list, and its Bukkit-levelsoftdepend:/depend:lists (all three never null; empty when absent or reading failed), and its declaredversion:andapi-version:as text (both nullable, like name and main), which the load-failure refusal quotes to identify the module.The answer to one catalogue version lookup, as the start-up update check needs it: a version was found, the catalogue confirmed it has nothing to offer, or the lookup failed (the catalogue could not be reached, answered with an error status, or sent a body that could not be read). -
Classes in com.ultikits.ultitools.utils used by com.ultikits.ultitools.utilsClassDescriptionThe four removed filter layers, in the exact order
isSafeClassNameevaluated them.An immutable view ofCloudAuthManager.status()'s result.The single owner of one UltiCloud login's entire lifetime.The outcome of aCredentialStore.read()call.One frame's match outcome: theEconomyUtils.MatchKind, plus the resolved module name when (and only when)kind == RESOLVED.The three possible outcomes of matching one stack frame againstprefixToModule(Codex P2, PR #463, round 3): a barenullreturn collapsed "this frame belongs to no registered module" and "this frame's closest root is claimed by two or more DIFFERENT modules" into the same value, and the last two review rounds both found a defect that traces straight back to that conflation — aNONEframe must let the per-frame walk continue outward (a real non-match, no evidence either way), while anAMBIGUOUSframe must terminate the walk immediately (real evidence that a module frame exists here, but WHICH module cannot be determined) — seeEconomyUtils.attributeModule(StackTraceElement[], Map)'s own javadoc for why continuing past an ambiguous frame is itself the bug.Progress callback interface for download operations.A fluent builder for creating ItemStacks with various properties.An extremely simple JSON builder.A super simple representation of a JSON object.Where the latest version of a module, and its download, come from.Named points of a transaction; a test crashes at one to reproduce that window.How a JAR is downloaded.A file a destructive step touches, and the recorded hashes it may hold; none means it must be absent.How files are moved and deleted; a test substitutes a failing one.File work that may fail with anIOException.A step found a file the transaction cannot identify; the record is held for the operator.The persisted record of one transaction.WhatModuleFileTransactions.recordedIdentity(com.ultikits.ultitools.utils.ModuleFileTransactions.Removal, java.io.File)found: the same file, a different file, or -- with the read error -- a file whose content could not be read to tell.A record whose names would leave their folder, or that this version does not understand.One file aREMOVErecord deletes at the next start, and what it was when recorded.A module an uninstall removed, in every form a transaction can name it by: the identify-strings and runtime names of the instances it unloaded (plus the argument it was given), and the file names of its JARs -- the ones those instances were loaded from, the ones the start-up scan recorded as declaring their main class, and the ones it deleted or recorded for deletion.One line for the start-up log, with its catalogue key and arguments.WhatModuleFileTransactions.reserve(com.ultikits.ultitools.utils.ModuleFileTransactions.Record, java.io.File, java.lang.String, java.util.List<com.ultikits.ultitools.abstracts.UltiToolsPlugin>, java.util.function.Function<com.ultikits.ultitools.abstracts.UltiToolsPlugin, java.io.File>)decided: the module and JAR to stage an update for, or the refusal.Which start-up step a rollback is finished from; it decides what the log line says.The outcome.A dispatch-table entry pairing a handler with theCapabilitythat must be enabled before it runs (D-10), and with which side records that decision's verdict in theRemoteActionLog(CR-01, 06-REVIEW.md).Which side of a capability-gated dispatch records theRemoteActionLogverdict for the enabled branch (CR-01, 06-REVIEW.md).What one archive says about which module it holds -- the single reader both identity resolution and entry classification use, so the two cannot drift apart.A catalogue answer whosedatais a string, with its HTTP status kept.What one entry of the modules folder is, relative to the module being uninstalled.Everything later decisions need about which module this is, resolved once.Raised when a module's own unload threw.What a filesystem probe answered, keeping "unknown" out of "no".What the module loader and the loaded instances say about an uninstall's targets, read before anything is unloaded.The uninstall could not delete these JARs now -- the running server holds them open, or the folder is not writable -- and has recorded them, so the next start deletes them before any module loads (#518).The uninstall could not delete these JARs now and could not record their deletion for the next start either (#518).The entries an uninstall could not identify, carried on whatever failure leaves the method.Raised when the uninstall refuses to act because its outcome would be undefined: two possible targets, or a target whose JAR another running module shares.What an uninstall did, and what it could not determine.The subset of a module'splugin.ymlthis framework needs: its declaredname:andmain:(both nullable - absent when the archive has none or reading failed), itsloadAfter:list, and its Bukkit-levelsoftdepend:/depend:lists (all three never null; empty when absent or reading failed), and its declaredversion:andapi-version:as text (both nullable, like name and main), which the load-failure refusal quotes to identify the module.Callbacks aPosixAttributePreserver.replaceInPlace(java.io.File, byte[], com.ultikits.ultitools.utils.PosixAttributePreserver.ReplaceInPlaceListener)caller supplies so each replace-in-place site can log accurate, resource-specific wording for exactly how the operation was declined or degraded -- this shared operation does not know or care whethertargetis a language catalogue or a provenance sidecar, only the caller does.The only thing that writes the UltiCloud credential to disk.What happened to a request.The result of one call: anUltiCloudRequests.Outcome, and for a completed exchange its status and body.The answer to one catalogue version lookup, as the start-up update check needs it: a version was found, the catalogue confirmed it has nothing to offer, or the lookup failed (the catalogue could not be reached, answered with an error status, or sent a body that could not be read).What the lookup established.