update docs

Author: hauner

docs/modules/ROOT/pages/index.adoc

@@ -36,7 +36,7 @@ The first step of the configuration is to add the plugin, and the processor(s) t
  <groupId>io.openapiprocessor</groupId>
  <artifactId>openapi-processor-maven-plugin</artifactId>
  <!-- update to the latest version, see maven central badge at top -->
- <version>2022.1</version>
+ <version>2024.1</version>
 
  <!-- ... next step ... -->
  </plugin>
@@ -54,12 +54,12 @@ The processors are dependencies of the plugin, and they are expected in the `<pl
  <dependency>
  <groupId>io.openapiprocessor</groupId>
  <artifactId>openapi-processor-spring</artifactId>
- <version>2022.1</version>
+ <version>2023.6.1</version>
  </dependency>
  <dependency>
  <groupId>io.openapiprocessor</groupId>
  <artifactId>openapi-processor-json</artifactId>
- <version>2021.2</version>
+ <version>2023.6.1</version>
  </dependency>
  </dependencies>
 
@@ -101,6 +101,9 @@ Here is an example to run `openapi-processor-spring` that explains the configura
  <configuration>
  <id>spring</id> <!--3-->
 
+ <!-- true is default -->
+ <addSourceRoot>true</addSourceRoot> <!--9-->
+
  <!--
  <apiPath>${project.basedir}/src/api/openapi.yaml</apiPath>
  --> <!--4-->
@@ -109,7 +112,7 @@ Here is an example to run `openapi-processor-spring` that explains the configura
  <values>
  <targetDir>${project.basedir}/target/generated-sources/openapi</targetDir> <!--6-->
  <mapping>${project.basedir}/src/api/mapping.yaml</mapping> <!--7-->
- <parser>OPENAPI4J</parser>
+ <parser>INTERNAL</parser>
  <showWarnings>true</showWarnings>
  </values>
 
@@ -150,7 +153,7 @@ To allow any level of nesting it is possible to create `*<nested/>*` option maps
 {
  "targetDir": "<basedir path>/target/generated-sources/openapi",
  "mapping": "<basedir path>/src/api/mapping.yaml",
- "parser": "OPENAPI4J",
+ "parser": "INTERNAL",
  "showWarnings":true,
  "foo": {
  "bar": "foo-bar"
@@ -164,6 +167,9 @@ To allow any level of nesting it is possible to create `*<nested/>*` option maps
 
 <8> `*<goal/>*` **goal** (mandatory): this is the goal maven should run. Since the plugin does only have a single goal the value is always `process`.
 
+<9> `*<addSourceRoot/>*` **addSourceRoot* (optional): this defaults to `true` and automatically adds the `targetDir` as compile source root folder. It can be disabled by setting it to `false`.
+
+=== multiple processors
 
 To run a second processor add another `<execution>` element. Here is an example that configures xref:spring:ROOT:index.adoc[openapi-processor-spring] and xref:json:ROOT:index.adoc[openapi-processor-json]:
 
@@ -244,67 +250,30 @@ With this configuration maven will use it when directly running the `process` go
 
 == using the processor output
 
-So far the plugin processes the given openapi yaml and writes the output to the given target directory but maven ignores the output.
-
-It is necessary to tell maven to use the generated files. In case of generated java source files maven should compile them. The *build-helper-maven-plugin* is used to for this:
-
-[source,xml]
-----
-<?xml version="1.0" encoding="UTF-8"?>
-<project xmlns="http://maven.apache.org/POM/4.0.0" ...>
- <build>
- <plugins>
- <plugin>
- <groupId>org.codehaus.mojo</groupId>
- <artifactId>build-helper-maven-plugin</artifactId>
- <executions>
- <execution>
- <id>oap-sources</id>
- <phase>generate-sources</phase>
- <goals>
- <goal>add-source</goal>
- </goals>
- <configuration>
- <sources>
- <source>${project.build.directory}/generated-sources/openapi</source>
- </sources>
- </configuration>
- </execution>
-
-
- </executions>
- </plugin>
+=== source files
 
- </plugins>
- </build>
-</project>
-----
+Starting with the release 2024.1 it is no longer necessary to manually add the generated sources to the build. The plugin will automatically add the `targetDir` as compile source root.
 
-This tells the *build-helper-maven-plugin* to add the processors `targetDir` as an additional source folder to the project.
+It can be disabled by setting the plugin configuration `<addSourceRoot>` to `false`.
 
-Maven will now include the generated files when it compiles the project.
+=== resource files
 
-If the output of the processor (e.g. generated by openapi-processor-json) should be used as resource the *build-helper-maven-plugin* has a goal for this too. Just add another `<excecution/>` using the `add-resource` goal:
+If the output of the processor (e.g. generated by openapi-processor-json) should be used as resource add a resource directory.
 
 [source,xml]
 ----
-<execution>
- <id>oap-resources</id>
- <phase>generate-resources</phase>
- <goals>
- <goal>add-resource</goal>
- </goals>
- <configuration>
+<?xml version="1.0" encoding="UTF-8"?>
+<project xmlns="http://maven.apache.org/POM/4.0.0" ...>
+ <build>
  <resources>
-  <resource>
-  <directory>${project.build.directory}/generated-resources/json</directory>
-  </resource>
+ <resource>
+ <directory>${project.build.directory}/generated-resources/json</directory>
+ </resource>
  </resources>
- </configuration>
-</execution>
+ </build>
+</project>
 ----
 
-
 == Samples
 
 See the maven sample in the xref:samples::index.adoc[samples] for a working spring boot example.