try (Writer writer = Files.newBufferedWriter(resumeProperties)) {
                properties.store(writer, null);
            }
        } catch (IOException e) {
            String message = "Could not create " + RESUME_PROPERTIES_FILENAME + " file.";
            throw new BuildResumptionPersistenceException(message, e);
        }
    }

   * to stop requests. You could poll for lifecycle changes in a work loop:
   *
   * <pre>
   *   public void run() {
   *     while ({@link #isRunning()}) {
   *       // perform a unit of work
   *     }
   *   }
   * </pre>
   *
   * <p>...or you could respond to stop requests by implementing {@link #triggerShutdown()}, which

 * governing permissions and limitations under the License.
 */
package org.codelibs.core.exception;

import java.lang.reflect.Field;

/**
 * Signals that a field could not be made accessible.
 */
public class BeanFieldSetAccessibleFailureException extends ClRuntimeException {
    private static final long serialVersionUID = 1L;

    /**
     * The target class.
     */

 * governing permissions and limitations under the License.
 */
package org.codelibs.core.exception;

import java.lang.reflect.Method;

/**
 * Signals that a method could not be made accessible.
 */
public class BeanMethodSetAccessibleFailureException extends ClRuntimeException {

    private static final long serialVersionUID = 1L;

    /**
     * The target class.
     */

     * @return The result of the settings building, never {@code null}.
     * @throws SettingsBuildingException If the effective settings could not be built.
     */
    SettingsBuildingResult build(SettingsBuildingRequest request) throws SettingsBuildingException;

You could load it at the top level of the module/file, but that would also mean that it would **load the model** even if you are just running a simple automated test, then that test would be **slow** because it would have to wait for the model to load before being able to run an independent part of the code.

    private final CoreExtension extension;

    public ExtensionResolutionException(CoreExtension extension, Throwable cause) {
        super(
                "Extension " + extension.getId() + " or one of its dependencies could not be resolved: "
                        + cause.getMessage(),
                cause);
        this.extension = extension;
    }

    public CoreExtension getExtension() {
        return extension;
    }

    private final String artifactId;

    public PluginVersionNotFoundException(String groupId, String artifactId) {
        super("The plugin '" + groupId + ":" + artifactId + "' does not exist or no valid version could be found");

        this.groupId = groupId;
        this.artifactId = artifactId;
    }

    public String getGroupId() {
        return groupId;
    }

    public String getArtifactId() {

     * </p>
     *
     * @param targetClass the target class (must not be {@literal null})
     * @return the class loader
     * @throws IllegalStateException if the class loader could not be obtained
     */
    public static ClassLoader getClassLoader(final Class<?> targetClass) {
        assertArgumentNotNull("targetClass", targetClass);

 * }
 * }
 *
 * @author Ben Yu
 * @since 12.0
 */
/*
 * A nullable bound would let users create a TypeParameter instance for a parameter with a nullable
 * bound. However, it would also let them create `new TypeParameter<@Nullable T>() {}`, which
 * wouldn't behave as users might expect. Additionally, it's not clear how the TypeToken API could
 * support even a "normal" `TypeParameter<T>` when `<T>` has a nullable bound. (See the discussion