com.diffplug.spotless.extra

Class EclipseBasedStepBuilder.State

java.lang.Object

com.diffplug.spotless.extra.EclipseBasedStepBuilder.State

All Implemented Interfaces:

Serializable

Enclosing class:

EclipseBasedStepBuilder

public static class EclipseBasedStepBuilder.State
extends Object
implements Serializable

State of Eclipse configuration items, providing functionality to derived information based on the state.

See Also:

Serialized Form

Constructor Summary

Constructors

Modifier	Constructor and Description
protected	State(String formatterStepExt, Provisioner jarProvisioner, List<String> dependencies, Iterable<File> settingsFiles) State constructor expects that all passed items are not modified afterwards

Method Summary

Modifier and Type	Method and Description
Optional<String>	getMavenCoordinate(String prefix) Returns first coordinate from sorted set that starts with a given prefix.
Properties	getPreferences() Get formatter preferences
Class<?>	loadClass(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(String formatterStepExt,
                Provisioner jarProvisioner,
                List<String> dependencies,
                Iterable<File> settingsFiles)
         throws IOException

State constructor expects that all passed items are not modified afterwards

Throws:

IOException

Method Detail

getPreferences

public Properties getPreferences()

Get formatter preferences

getMavenCoordinate

public Optional<String> getMavenCoordinate(String prefix)

Returns first coordinate from sorted set that starts with a given prefix.

loadClass

public Class<?> loadClass(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)