You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Maven the mechanism for adding additional classes to the plugin classpath is via plugin dependencies. I hope that Gradle provides something similar.
The text was updated successfully, but these errors were encountered:
"Multiple steps with name '" + newStep.getName() + "' for spotless format '" + formatName() + "'");
}
steps.add(newStep);
}
For Maven, the problem is the DSL. How do you configure which targets the new step applies to? Happy to take a design and then PR for a plugin SPI, but it should be maven only. I recommend writing the docs first.
Currently adding a custom plugin requires adaptations to the Maven/Gradle plugin as
a) FormatterStepFactory and
b) FormatterFactory or FormatExtension
are
a) not build system agnostic and
b) are not dynamically looked up
It would be beneficial to have a build-agnostic plugin SPI which allows to
a) load dependencies
b) pass configuration
c) dynamically lookup services from classpath (e.g. with https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/util/ServiceLoader.html)
For Maven the mechanism for adding additional classes to the plugin classpath is via plugin dependencies. I hope that Gradle provides something similar.
The text was updated successfully, but these errors were encountered: