Package com.diffplug.spotless.extra

Class EclipseBasedStepBuilder.State

  • All Implemented Interfaces:
    java.io.Serializable
    Enclosing class:
    EclipseBasedStepBuilder
    public static class EclipseBasedStepBuilder.State
extends java.lang.Object
implements java.io.Serializable
    State of Eclipse configuration items, providing functionality to derived information based on the state.
    See Also:
    Serialized Form

    • Constructor Summary

      Constructors 
      Modifier Constructor Description
      protected State​(java.lang.String formatterVersion, java.lang.String formatterStepExt, JarState jarState, FileSignature settingsFiles)
      State constructor expects that all passed items are not modified afterwards

    • Method Summary

      All Methods Instance Methods Concrete Methods 
      Modifier and Type Method Description
      java.util.Properties getPreferences()
      Get formatter preferences
      java.lang.String getSemanticVersion()  
      java.lang.Class<?> loadClass​(java.lang.String name)
      Load class based on the given configuration of JAR provider and Maven coordinates.

      • Methods inherited from class java.lang.Object

        clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

    • Constructor Detail

      • State

        protected State​(java.lang.String formatterVersion,
                java.lang.String formatterStepExt,
                JarState jarState,
                FileSignature settingsFiles)
        State constructor expects that all passed items are not modified afterwards

    • Method Detail

      • getSemanticVersion

        public java.lang.String getSemanticVersion()

      • getPreferences

        public java.util.Properties getPreferences()
        Get formatter preferences

      • loadClass

        public java.lang.Class<?> loadClass​(java.lang.String name)
        Load class based on the given configuration of JAR provider and Maven coordinates. Different class loader instances are provided in the following scenarios:
        1. The JARs (jarState) have changes (this should only occur during development)
        2. Different configurations (settingsFiles) are used for different sub-projects
        3. The same Eclipse step implementation provides different formatter types (formatterStepExt)