Uses of Class
com.ultikits.ultitools.utils.ModuleFileTransactions.Expected

Packages that use ModuleFileTransactions.Expected

Package	Description
com.ultikits.ultitools.utils

Uses of ModuleFileTransactions.Expected in com.ultikits.ultitools.utils

Methods in com.ultikits.ultitools.utils that return ModuleFileTransactions.Expected

Modifier and Type	Method	Description
private static ModuleFileTransactions.Expected	ModuleFileTransactions.may(File file, String... hashes)	file may be absent, or hold one of hashes; with none given it must be absent.
private static ModuleFileTransactions.Expected	ModuleFileTransactions.must(File file, String hash)	file must be there and hold hash.

Methods in com.ultikits.ultitools.utils with parameters of type ModuleFileTransactions.Expected

Modifier and Type	Method	Description
private void	ModuleFileTransactions.requireRecorded(ModuleFileTransactions.Record record, ModuleFileTransactions.Expected... expected)	The foreign-file rule, at every destructive step: the transaction only ever moves, replaces or deletes a file whose SHA-256 matches the record -- the staged new JAR or the kept old JAR -- and only into a place that is free.
private static String	ModuleFileTransactions.unexpected(ModuleFileTransactions.Expected expected)	What is wrong with one expected file, or null when it is as recorded.