diff --git a/plug-in-development/index.html b/plug-in-development/index.html index 0e112c6..a814660 100644 --- a/plug-in-development/index.html +++ b/plug-in-development/index.html @@ -124,69 +124,69 @@ class JavaBuildGenerator: IInitContributor { Description - + IBuildConfigFieldContributor - IInterceptor + IInterceptor Plug-ins that want to add custom fields to the generated BuildConfig class. - IBuildDirectoryInterceptor - IInterceptor + IBuildDirectoryInterceptor + IInterceptor Plug-ins that need to generate class files in a different directory than the default one should implement this interface. - IClasspathContributor + IClasspathContributor - IContributor + IContributor Classpath contributors let you specify additional jar files or directories that will be used by the "compile" task. - IClasspathInterceptor + IClasspathInterceptor - IInterceptor + IInterceptor Plug-ins that want to modify the classpath before Kobalt uses it should implement this interface. - ICompilerContributor - IContributor + ICompilerContributor + IContributor Plug-ins that know how to turn files into bytecodes should implement this interface. - ICompilerFlagContributor - IContributor + ICompilerFlagContributor + IContributor Plug-ins that need to add flags to the compiler. - ICompilerInterceptor - IInterceptor + ICompilerInterceptor + IInterceptor Plug-ins that implement this interface get a chance to alter the dependencies of a project (dependencies{}, dependenciesTest{}, ...) before Kobalt sees them. - IDocContributor - IContributor + IDocContributor + IContributor Plug-ins that know how to generate documentation out of source files should implement this interface. - IInitContributor - IContributor + IInitContributor + IContributor When invoked with --init followed by archetype names separated by commas, Kobalt will invoke each of these contributors so they can generate their files. Archetypes are useful to create projects from scratch with a minimal number of @@ -195,15 +195,15 @@ class JavaBuildGenerator: IInitContributor { - IProjectContributor - IContributor + IProjectContributor + IContributor Some plug-ins produce projects (Java, Kotlin) while others don't (Packaging, Application, etc...). The ones that do need to register themselves as project contributors. This is how Kobalt collects all the projects defined after a build file was parsed. - IRepoContributor - IContributor + IRepoContributor + IContributor Some plug-ins might want to add their own repository to the list of repositories that Kobalt already supports. This is the case of the Android plug-in which, once the ANDROID_HOME environment variable has been @@ -212,16 +212,16 @@ class JavaBuildGenerator: IInitContributor { - IRunnerContributor - IContributor + IRunnerContributor + IContributor Plug-ins that can operate when the "run" task gets invoked should implement that interface. - + ISourceDirectoryContributor - IContributor + IContributor Plug-ins that add source directories. @@ -229,25 +229,25 @@ class JavaBuildGenerator: IInitContributor { - + ISourceDirectoryInterceptor - IInterceptor + IInterceptor Plug-ins that want to add, remove or alter the source directories should implement this interface. - + ITestRunnerContributor - IContributor + IContributor Plug-ins that can operate when the "test" task gets invoked should implement that interface. - + ITestSourceDirectoryContributor - IContributor + IContributor Plug-ins that add test source directories. @@ -276,7 +276,7 @@ interface IProjectAffinity { fun affinity(project: Project, context: KobaltContext) : Int }

- For example, the JavaPlugin implements the ICompilerContributor interface and then overrides + For example, the JavaPlugin implements the ICompilerContributor interface and then overrides the affinity() method to make sure it gets run for Java projects but ignored for others: