You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by da...@apache.org on 2023/03/01 19:06:22 UTC
[causeway] 02/02: CAUSEWAY-3252: adds workaround for lombok annotation processor
This is an automated email from the ASF dual-hosted git repository.
danhaywood pushed a commit to branch CAUSEWAY-3252
in repository https://gitbox.apache.org/repos/asf/causeway.git
commit e0113c1ead6e7e8da49b87944a18b22e5d5229fe
Author: danhaywood <da...@haywood-associates.co.uk>
AuthorDate: Wed Mar 1 19:06:12 2023 +0000
CAUSEWAY-3252: adds workaround for lombok annotation processor
while JDO modules work ok without the workaround (meaning that the Qxxx classes are now generated)
---
antora/lombok.processor | 10 ++++
api/applib/lombok.processor | 10 ++++
api/schema/lombok.processor | 10 ++++
bom/lombok.processor | 10 ++++
bom/pom.xml | 60 +++++++---------------
commons/lombok.processor | 10 ++++
commons/pom.xml | 33 +++++++++++-
core/codegen-bytebuddy/lombok.processor | 10 ++++
core/codegen-bytebuddy/pom.xml | 40 +++++++++++----
core/config/lombok.processor | 10 ++++
core/interaction/lombok.processor | 10 ++++
core/internaltestsupport/lombok.processor | 10 ++++
core/lombok.processor | 10 ++++
core/metamodel/lombok.processor | 10 ++++
core/runtime/lombok.processor | 10 ++++
core/runtimeservices/lombok.processor | 10 ++++
core/security/lombok.processor | 10 ++++
core/transaction/lombok.processor | 10 ++++
core/webapp/lombok.processor | 10 ++++
examples/demo/domain-tests/lombok.processor | 10 ++++
examples/demo/domain/lombok.processor | 10 ++++
examples/demo/javafx/lombok.processor | 10 ++++
examples/demo/lombok.processor | 10 ++++
examples/demo/vaadin/lombok.processor | 10 ++++
examples/demo/web/lombok.processor | 10 ++++
examples/demo/wicket/common/lombok.processor | 10 ++++
examples/demo/wicket/jdo/lombok.processor | 10 ++++
.../demo/wicket/jpa-and-graphql/lombok.processor | 10 ++++
examples/demo/wicket/jpa/lombok.processor | 10 ++++
extensions/core/commandlog/applib/lombok.processor | 10 ++++
extensions/core/commandlog/lombok.processor | 10 ++++
.../commandlog/persistence-jpa/lombok.processor | 10 ++++
extensions/core/docgen/lombok.processor | 10 ++++
extensions/core/excel/applib/lombok.processor | 10 ++++
extensions/core/excel/fixture/lombok.processor | 10 ++++
extensions/core/excel/integtests/lombok.processor | 10 ++++
extensions/core/excel/lombok.processor | 10 ++++
extensions/core/excel/testing/lombok.processor | 10 ++++
.../core/executionlog/applib/lombok.processor | 10 ++++
extensions/core/executionlog/lombok.processor | 10 ++++
.../executionlog/persistence-jpa/lombok.processor | 10 ++++
.../core/executionoutbox/applib/lombok.processor | 10 ++++
extensions/core/executionoutbox/lombok.processor | 10 ++++
.../persistence-jpa/lombok.processor | 10 ++++
.../executionoutbox/restclient/lombok.processor | 10 ++++
.../executionrepublisher/applib/lombok.processor | 10 ++++
.../core/executionrepublisher/lombok.processor | 10 ++++
extensions/core/flyway/impl/lombok.processor | 10 ++++
extensions/core/flyway/lombok.processor | 10 ++++
extensions/lombok.processor | 10 ++++
.../security/audittrail/applib/lombok.processor | 10 ++++
extensions/security/audittrail/lombok.processor | 10 ++++
.../audittrail/persistence-jpa/lombok.processor | 10 ++++
extensions/security/secman/applib/lombok.processor | 10 ++++
.../secman/delegated-shiro/lombok.processor | 10 ++++
.../secman/delegated-springoauth2/lombok.processor | 10 ++++
.../secman/encryption-jbcrypt/lombok.processor | 10 ++++
.../secman/encryption-spring/lombok.processor | 10 ++++
.../security/secman/integration/lombok.processor | 10 ++++
extensions/security/secman/lombok.processor | 10 ++++
.../secman/persistence-jpa/lombok.processor | 10 ++++
.../security/sessionlog/applib/lombok.processor | 10 ++++
extensions/security/sessionlog/lombok.processor | 10 ++++
.../sessionlog/persistence-jpa/lombok.processor | 10 ++++
.../shiro-realm-ldap/impl/lombok.processor | 10 ++++
.../security/shiro-realm-ldap/lombok.processor | 10 ++++
extensions/security/spring-oauth2/lombok.processor | 10 ++++
.../adoc/modules/spring-oauth2/pages/about.adoc | 2 +-
extensions/vro/cors/impl/lombok.processor | 10 ++++
extensions/vro/cors/lombok.processor | 10 ++++
extensions/vw/exceldownload/lombok.processor | 10 ++++
.../vw/exceldownload/wicket-ui/lombok.processor | 10 ++++
extensions/vw/fullcalendar/applib/lombok.processor | 10 ++++
extensions/vw/fullcalendar/lombok.processor | 10 ++++
.../wicket/integration/lombok.processor | 10 ++++
extensions/vw/fullcalendar/wicket/lombok.processor | 10 ++++
.../vw/fullcalendar/wicket/ui/lombok.processor | 10 ++++
extensions/vw/pdfjs/applib/lombok.processor | 10 ++++
extensions/vw/pdfjs/fixtures/lombok.processor | 10 ++++
extensions/vw/pdfjs/lombok.processor | 10 ++++
extensions/vw/pdfjs/metamodel/lombok.processor | 10 ++++
.../vw/pdfjs/wicket/integration/lombok.processor | 10 ++++
extensions/vw/pdfjs/wicket/lombok.processor | 10 ++++
extensions/vw/pdfjs/wicket/ui/lombok.processor | 10 ++++
extensions/vw/sse/applib/lombok.processor | 10 ++++
extensions/vw/sse/lombok.processor | 10 ++++
extensions/vw/sse/metamodel/lombok.processor | 10 ++++
extensions/vw/sse/wicket/lombok.processor | 10 ++++
incubator/clients/kroviz/lombok.processor | 10 ++++
incubator/core/jsr303/lombok.processor | 10 ++++
.../extensions/core/commandreplay/lombok.processor | 10 ++++
.../core/commandreplay/primary/lombok.processor | 10 ++++
.../core/commandreplay/secondary/lombok.processor | 10 ++++
incubator/lombok.processor | 10 ++++
incubator/viewers/graphql/applib/lombok.processor | 10 ++++
incubator/viewers/graphql/lombok.processor | 10 ++++
incubator/viewers/graphql/model/lombok.processor | 10 ++++
incubator/viewers/graphql/test/lombok.processor | 10 ++++
incubator/viewers/graphql/viewer/lombok.processor | 10 ++++
incubator/viewers/javafx/lombok.processor | 10 ++++
incubator/viewers/javafx/model/lombok.processor | 10 ++++
incubator/viewers/javafx/ui/lombok.processor | 10 ++++
incubator/viewers/javafx/viewer/lombok.processor | 10 ++++
incubator/viewers/vaadin/lombok.processor | 10 ++++
incubator/viewers/vaadin/model/lombok.processor | 10 ++++
incubator/viewers/vaadin/ui/lombok.processor | 10 ++++
incubator/viewers/vaadin/viewer/lombok.processor | 10 ++++
lombok.processor | 10 ++++
mavendeps/lombok.processor | 10 ++++
mavendeps/webapp/lombok.processor | 10 ++++
persistence/commons/lombok.processor | 10 ++++
persistence/jdo/applib/lombok.processor | 10 ++++
persistence/jdo/datanucleus/lombok.processor | 10 ++++
persistence/jdo/integration/lombok.processor | 10 ++++
persistence/jdo/lombok.processor | 10 ++++
persistence/jdo/metamodel/lombok.processor | 10 ++++
persistence/jdo/provider/lombok.processor | 10 ++++
persistence/jdo/spring/lombok.processor | 10 ++++
persistence/jpa/applib/lombok.processor | 10 ++++
persistence/jpa/eclipselink/lombok.processor | 10 ++++
persistence/jpa/integration/lombok.processor | 10 ++++
persistence/jpa/lombok.processor | 10 ++++
persistence/jpa/metamodel/lombok.processor | 10 ++++
regressiontests/incubating/lombok.processor | 10 ++++
regressiontests/lombok.processor | 10 ++++
.../stable-bootstrapping/lombok.processor | 10 ++++
.../generic/lombok.processor | 10 ++++
.../stable-cmdexecauditsess/lombok.processor | 10 ++++
.../persistence-jdo/lombok.processor | 10 ++++
.../persistence-jpa/lombok.processor | 10 ++++
regressiontests/stable-config/lombok.processor | 10 ++++
.../stable-core-wrapperfactory/lombok.processor | 10 ++++
regressiontests/stable-cucumber/lombok.processor | 10 ++++
.../stable-domainmodel/lombok.processor | 10 ++++
.../stable-eventhandling/lombok.processor | 10 ++++
regressiontests/stable-factory/lombok.processor | 10 ++++
regressiontests/stable-interact/lombok.processor | 10 ++++
regressiontests/stable-layouts/lombok.processor | 10 ++++
.../stable-persistence-jdo/lombok.processor | 10 ++++
.../stable-persistence-jpa/lombok.processor | 10 ++++
.../stable-publishing-jpa/lombok.processor | 10 ++++
regressiontests/stable-rest/lombok.processor | 10 ++++
regressiontests/stable-value/lombok.processor | 10 ++++
.../stable-viewers-common/lombok.processor | 10 ++++
.../stable-viewers-jdo/lombok.processor | 10 ++++
.../stable-viewers-jpa/lombok.processor | 10 ++++
regressiontests/stable/lombok.processor | 10 ++++
security/bypass/lombok.processor | 10 ++++
security/keycloak/lombok.processor | 10 ++++
security/shiro/lombok.processor | 10 ++++
security/spring/lombok.processor | 10 ++++
starters/lombok.processor | 10 ++++
supplemental-model/lombok.processor | 10 ++++
testing/archtestsupport/applib/lombok.processor | 10 ++++
testing/archtestsupport/lombok.processor | 10 ++++
testing/fakedata/applib/lombok.processor | 10 ++++
testing/fakedata/fixtures/lombok.processor | 10 ++++
testing/fakedata/integtests/lombok.processor | 10 ++++
testing/fakedata/lombok.processor | 10 ++++
testing/fixtures/applib/lombok.processor | 10 ++++
testing/fixtures/lombok.processor | 10 ++++
testing/h2console/lombok.processor | 10 ++++
testing/h2console/ui/lombok.processor | 10 ++++
testing/hsqldbmgr/lombok.processor | 10 ++++
testing/hsqldbmgr/ui/lombok.processor | 10 ++++
testing/integtestsupport/applib/lombok.processor | 10 ++++
testing/integtestsupport/lombok.processor | 10 ++++
testing/lombok.processor | 10 ++++
testing/specsupport/applib/lombok.processor | 10 ++++
testing/specsupport/lombok.processor | 10 ++++
testing/unittestsupport/applib/lombok.processor | 10 ++++
testing/unittestsupport/lombok.processor | 10 ++++
tooling/c4modeling/lombok.processor | 10 ++++
tooling/cli/lombok.processor | 10 ++++
tooling/java2adoc/lombok.processor | 10 ++++
tooling/javamodel/lombok.processor | 10 ++++
tooling/lombok.processor | 10 ++++
tooling/metaprog/lombok.processor | 10 ++++
tooling/model4adoc/lombok.processor | 10 ++++
tooling/projectmodel/lombok.processor | 10 ++++
valuetypes/asciidoc/applib/lombok.processor | 10 ++++
valuetypes/asciidoc/lombok.processor | 10 ++++
valuetypes/asciidoc/metamodel/lombok.processor | 10 ++++
.../asciidoc/persistence-jdo/lombok.processor | 10 ++++
.../asciidoc/persistence-jpa/lombok.processor | 10 ++++
valuetypes/asciidoc/ui/lombok.processor | 10 ++++
valuetypes/asciidoc/ui/vaadin/lombok.processor | 10 ++++
valuetypes/asciidoc/ui/wicket/lombok.processor | 10 ++++
valuetypes/jodatime/applib/lombok.processor | 10 ++++
valuetypes/jodatime/integration/lombok.processor | 10 ++++
valuetypes/jodatime/lombok.processor | 10 ++++
valuetypes/lombok.processor | 10 ++++
valuetypes/markdown/applib/lombok.processor | 10 ++++
valuetypes/markdown/lombok.processor | 10 ++++
valuetypes/markdown/metamodel/lombok.processor | 10 ++++
.../markdown/persistence-jdo/lombok.processor | 10 ++++
.../markdown/persistence-jpa/lombok.processor | 10 ++++
valuetypes/markdown/ui/lombok.processor | 10 ++++
valuetypes/markdown/ui/wicket/lombok.processor | 10 ++++
valuetypes/vega/applib/lombok.processor | 10 ++++
valuetypes/vega/lombok.processor | 10 ++++
valuetypes/vega/metamodel/lombok.processor | 10 ++++
valuetypes/vega/persistence-jdo/lombok.processor | 10 ++++
valuetypes/vega/persistence-jpa/lombok.processor | 10 ++++
valuetypes/vega/ui/lombok.processor | 10 ++++
valuetypes/vega/ui/vaadin/lombok.processor | 10 ++++
valuetypes/vega/ui/wicket/lombok.processor | 10 ++++
viewers/commons/applib/lombok.processor | 10 ++++
viewers/commons/lombok.processor | 10 ++++
viewers/commons/model/lombok.processor | 10 ++++
viewers/commons/prism/lombok.processor | 10 ++++
viewers/commons/services/lombok.processor | 10 ++++
viewers/restfulobjects/applib/lombok.processor | 10 ++++
viewers/restfulobjects/client/lombok.processor | 10 ++++
.../restfulobjects/jaxrs-resteasy/lombok.processor | 10 ++++
viewers/restfulobjects/lombok.processor | 10 ++++
viewers/restfulobjects/rendering/lombok.processor | 10 ++++
viewers/restfulobjects/testing/lombok.processor | 10 ++++
viewers/restfulobjects/viewer/lombok.processor | 10 ++++
viewers/wicket/applib/lombok.processor | 10 ++++
viewers/wicket/graceful/lombok.processor | 10 ++++
viewers/wicket/lombok.processor | 10 ++++
viewers/wicket/model/lombok.processor | 10 ++++
viewers/wicket/ui/lombok.processor | 10 ++++
viewers/wicket/viewer/lombok.processor | 10 ++++
225 files changed, 2292 insertions(+), 53 deletions(-)
diff --git a/antora/lombok.processor b/antora/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/antora/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/api/applib/lombok.processor b/api/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/api/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/api/schema/lombok.processor b/api/schema/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/api/schema/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/bom/lombok.processor b/bom/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/bom/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/bom/pom.xml b/bom/pom.xml
index a5bfd7abe9..db51652819 100644
--- a/bom/pom.xml
+++ b/bom/pom.xml
@@ -60,6 +60,8 @@ It is therefore a copy of org.apache:apache, with customisations clearly identif
<minimalMavenBuildVersion>3.8.0</minimalMavenBuildVersion> <!-- enforces https repos -->
<minimalJavaBuildVersion>11</minimalJavaBuildVersion>
<maven.compiler.release>11</maven.compiler.release>
+ <maven.compiler.source>11</maven.compiler.source>
+ <maven.compiler.target>11</maven.compiler.target>
<!-- for m-plugin-p and maven-plugin-annotations -->
<assembly.tarLongFileMode>posix</assembly.tarLongFileMode>
@@ -2133,15 +2135,6 @@ It is therefore a copy of org.apache:apache, with customisations clearly identif
</dependencies>
</dependencyManagement>
- <dependencies>
- <dependency>
- <groupId>org.projectlombok</groupId>
- <artifactId>lombok</artifactId>
- <version>${lombok.version}</version>
- <scope>provided</scope>
- </dependency>
- </dependencies>
-
<repositories>
<!-- breaks dependabot run: timeout due to repo not accessible
<repository>
@@ -2239,20 +2232,9 @@ It is therefore a copy of org.apache:apache, with customisations clearly identif
<artifactId>maven-compiler-plugin</artifactId>
<version>${maven-compiler-plugin.version}</version>
<configuration>
- <source>${maven.compiler.release}</source>
- <target>${maven.compiler.release}</target>
<showDeprecation>true</showDeprecation>
<showWarnings>true</showWarnings>
- <!-- Java compliance level, to be overridden with option maven.compiler.release -->
-<!--
- <annotationProcessorPaths>
- <path>
- <groupId>org.projectlombok</groupId>
- <artifactId>lombok</artifactId>
- <version>${lombok.version}</version>
- </path>
- </annotationProcessorPaths>
--->
+ <parameters>true</parameters>
</configuration>
<!-- goal:compile binds to phase:compile -->
<!-- goal:testCompile binds to phase:test-compile -->
@@ -3055,7 +3037,18 @@ It is therefore a copy of org.apache:apache, with customisations clearly identif
<artifactId>datanucleus-maven-plugin</artifactId>
<inherited>true</inherited>
</plugin>
-<!--
+ </plugins>
+ </build>
+ </profile>
+ <profile>
+ <id>causeway-app-lombok</id>
+ <activation>
+ <file>
+ <exists>${basedir}/lombok.processor</exists>
+ </file>
+ </activation>
+ <build>
+ <plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
@@ -3063,34 +3056,19 @@ It is therefore a copy of org.apache:apache, with customisations clearly identif
<configuration>
<showDeprecation>true</showDeprecation>
<showWarnings>true</showWarnings>
+ <parameters>true</parameters>
<annotationProcessorPaths>
- <path>
+ <!-- this is a workaround, should be picked up implicitly but yet not, for some reason -->
+ <annotationProcessorPath>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<version>${lombok.version}</version>
- </path>
- <path>
- <groupId>org.datanucleus</groupId>
- <artifactId>datanucleus-jdo-query</artifactId>
- <version>${datanucleus-jdo-query.version}</version>
- </path>
+ </annotationProcessorPath>
</annotationProcessorPaths>
</configuration>
</plugin>
--->
-
</plugins>
</build>
-<!--
- <dependencies>
- <dependency>
- <groupId>org.datanucleus</groupId>
- <artifactId>javax.jdo</artifactId>
- <version>${datanucleus-jdo-api.version}</version>
- <scope>provided</scope> <!– for datanucleus-jdo-query annotation processor, brought in via profile –>
- </dependency>
- </dependencies>
--->
</profile>
<profile>
<id>only-eclipse</id>
diff --git a/commons/lombok.processor b/commons/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/commons/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/commons/pom.xml b/commons/pom.xml
index 5203bd05fa..4bfd63a95d 100644
--- a/commons/pom.xml
+++ b/commons/pom.xml
@@ -51,6 +51,28 @@
</excludes>
</resource>
</resources>
+<!--
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <version>${maven-compiler-plugin.version}</version>
+ <configuration>
+ <showDeprecation>true</showDeprecation>
+ <showWarnings>true</showWarnings>
+ <parameters>true</parameters>
+ <annotationProcessorPaths>
+ <!– this is a workaround, should be picked up implicitly but yet not, for some reason –>
+ <annotationProcessorPath>
+ <groupId>org.projectlombok</groupId>
+ <artifactId>lombok</artifactId>
+ <version>${lombok.version}</version>
+ </annotationProcessorPath>
+ </annotationProcessorPaths>
+ </configuration>
+ </plugin>
+ </plugins>
+-->
</build>
<dependencies>
@@ -211,6 +233,15 @@
<scope>test</scope>
</dependency>
- </dependencies>
+ <!-- provided -->
+ <dependency>
+ <groupId>org.projectlombok</groupId>
+ <artifactId>lombok</artifactId>
+ <version>${lombok.version}</version>
+ <scope>provided</scope>
+ </dependency>
+
+ </dependencies>
+
</project>
diff --git a/core/codegen-bytebuddy/lombok.processor b/core/codegen-bytebuddy/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/codegen-bytebuddy/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/codegen-bytebuddy/pom.xml b/core/codegen-bytebuddy/pom.xml
index 9c6238e09a..9d412dc4d8 100644
--- a/core/codegen-bytebuddy/pom.xml
+++ b/core/codegen-bytebuddy/pom.xml
@@ -1,13 +1,13 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor
- license agreements. See the NOTICE file distributed with this work for additional
- information regarding copyright ownership. The ASF licenses this file to
- you under the Apache License, Version 2.0 (the "License"); you may not use
- this file except in compliance with the License. You may obtain a copy of
- the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required
- by applicable law or agreed to in writing, software distributed under the
- License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS
- OF ANY KIND, either express or implied. See the License for the specific
+<!-- Licensed to the Apache Software Foundation (ASF) under one or more contributor
+ license agreements. See the NOTICE file distributed with this work for additional
+ information regarding copyright ownership. The ASF licenses this file to
+ you under the Apache License, Version 2.0 (the "License"); you may not use
+ this file except in compliance with the License. You may obtain a copy of
+ the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required
+ by applicable law or agreed to in writing, software distributed under the
+ License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS
+ OF ANY KIND, either express or implied. See the License for the specific
language governing permissions and limitations under the License. -->
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -49,6 +49,26 @@
</excludes>
</resource>
</resources>
+ <plugins>
+ <plugin>
+ <groupId>org.apache.maven.plugins</groupId>
+ <artifactId>maven-compiler-plugin</artifactId>
+ <version>${maven-compiler-plugin.version}</version>
+ <configuration>
+ <showDeprecation>true</showDeprecation>
+ <showWarnings>true</showWarnings>
+ <parameters>true</parameters>
+ <annotationProcessorPaths>
+ <!-- this is a workaround, should be picked up implicitly but yet not, for some reason -->
+ <annotationProcessorPath>
+ <groupId>org.projectlombok</groupId>
+ <artifactId>lombok</artifactId>
+ <version>${lombok.version}</version>
+ </annotationProcessorPath>
+ </annotationProcessorPaths>
+ </configuration>
+ </plugin>
+ </plugins>
</build>
<dependencies>
@@ -73,4 +93,4 @@
</dependencies>
-</project>
\ No newline at end of file
+</project>
diff --git a/core/config/lombok.processor b/core/config/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/config/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/interaction/lombok.processor b/core/interaction/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/interaction/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/internaltestsupport/lombok.processor b/core/internaltestsupport/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/internaltestsupport/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/lombok.processor b/core/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/metamodel/lombok.processor b/core/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/runtime/lombok.processor b/core/runtime/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/runtime/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/runtimeservices/lombok.processor b/core/runtimeservices/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/runtimeservices/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/security/lombok.processor b/core/security/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/security/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/transaction/lombok.processor b/core/transaction/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/transaction/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/core/webapp/lombok.processor b/core/webapp/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/core/webapp/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/domain-tests/lombok.processor b/examples/demo/domain-tests/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/domain-tests/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/domain/lombok.processor b/examples/demo/domain/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/domain/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/javafx/lombok.processor b/examples/demo/javafx/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/javafx/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/lombok.processor b/examples/demo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/vaadin/lombok.processor b/examples/demo/vaadin/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/vaadin/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/web/lombok.processor b/examples/demo/web/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/web/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/wicket/common/lombok.processor b/examples/demo/wicket/common/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/wicket/common/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/wicket/jdo/lombok.processor b/examples/demo/wicket/jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/wicket/jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/wicket/jpa-and-graphql/lombok.processor b/examples/demo/wicket/jpa-and-graphql/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/wicket/jpa-and-graphql/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/examples/demo/wicket/jpa/lombok.processor b/examples/demo/wicket/jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/examples/demo/wicket/jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/commandlog/applib/lombok.processor b/extensions/core/commandlog/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/commandlog/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/commandlog/lombok.processor b/extensions/core/commandlog/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/commandlog/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/commandlog/persistence-jpa/lombok.processor b/extensions/core/commandlog/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/commandlog/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/docgen/lombok.processor b/extensions/core/docgen/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/docgen/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/excel/applib/lombok.processor b/extensions/core/excel/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/excel/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/excel/fixture/lombok.processor b/extensions/core/excel/fixture/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/excel/fixture/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/excel/integtests/lombok.processor b/extensions/core/excel/integtests/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/excel/integtests/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/excel/lombok.processor b/extensions/core/excel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/excel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/excel/testing/lombok.processor b/extensions/core/excel/testing/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/excel/testing/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionlog/applib/lombok.processor b/extensions/core/executionlog/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionlog/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionlog/lombok.processor b/extensions/core/executionlog/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionlog/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionlog/persistence-jpa/lombok.processor b/extensions/core/executionlog/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionlog/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionoutbox/applib/lombok.processor b/extensions/core/executionoutbox/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionoutbox/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionoutbox/lombok.processor b/extensions/core/executionoutbox/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionoutbox/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionoutbox/persistence-jpa/lombok.processor b/extensions/core/executionoutbox/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionoutbox/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionoutbox/restclient/lombok.processor b/extensions/core/executionoutbox/restclient/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionoutbox/restclient/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionrepublisher/applib/lombok.processor b/extensions/core/executionrepublisher/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionrepublisher/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/executionrepublisher/lombok.processor b/extensions/core/executionrepublisher/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/executionrepublisher/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/flyway/impl/lombok.processor b/extensions/core/flyway/impl/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/flyway/impl/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/core/flyway/lombok.processor b/extensions/core/flyway/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/core/flyway/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/lombok.processor b/extensions/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/audittrail/applib/lombok.processor b/extensions/security/audittrail/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/audittrail/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/audittrail/lombok.processor b/extensions/security/audittrail/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/audittrail/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/audittrail/persistence-jpa/lombok.processor b/extensions/security/audittrail/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/audittrail/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/applib/lombok.processor b/extensions/security/secman/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/delegated-shiro/lombok.processor b/extensions/security/secman/delegated-shiro/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/delegated-shiro/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/delegated-springoauth2/lombok.processor b/extensions/security/secman/delegated-springoauth2/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/delegated-springoauth2/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/encryption-jbcrypt/lombok.processor b/extensions/security/secman/encryption-jbcrypt/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/encryption-jbcrypt/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/encryption-spring/lombok.processor b/extensions/security/secman/encryption-spring/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/encryption-spring/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/integration/lombok.processor b/extensions/security/secman/integration/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/integration/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/lombok.processor b/extensions/security/secman/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/secman/persistence-jpa/lombok.processor b/extensions/security/secman/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/secman/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/sessionlog/applib/lombok.processor b/extensions/security/sessionlog/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/sessionlog/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/sessionlog/lombok.processor b/extensions/security/sessionlog/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/sessionlog/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/sessionlog/persistence-jpa/lombok.processor b/extensions/security/sessionlog/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/sessionlog/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/shiro-realm-ldap/impl/lombok.processor b/extensions/security/shiro-realm-ldap/impl/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/shiro-realm-ldap/impl/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/shiro-realm-ldap/lombok.processor b/extensions/security/shiro-realm-ldap/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/shiro-realm-ldap/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/spring-oauth2/lombok.processor b/extensions/security/spring-oauth2/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/security/spring-oauth2/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/security/spring-oauth2/src/main/adoc/modules/spring-oauth2/pages/about.adoc b/extensions/security/spring-oauth2/src/main/adoc/modules/spring-oauth2/pages/about.adoc
index 9d58f0842e..6f8e794834 100644
--- a/extensions/security/spring-oauth2/src/main/adoc/modules/spring-oauth2/pages/about.adoc
+++ b/extensions/security/spring-oauth2/src/main/adoc/modules/spring-oauth2/pages/about.adoc
@@ -128,7 +128,7 @@ public class AppManifest {
}
----
-Next configure authenticationStrategy and permissenResolver for realms, and add the userId:
+Next configure authenticationStrategy and permissionResolver for realms, and add the userId:
[source,ini]
.shiro.ini
diff --git a/extensions/vro/cors/impl/lombok.processor b/extensions/vro/cors/impl/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vro/cors/impl/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vro/cors/lombok.processor b/extensions/vro/cors/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vro/cors/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/exceldownload/lombok.processor b/extensions/vw/exceldownload/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/exceldownload/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/exceldownload/wicket-ui/lombok.processor b/extensions/vw/exceldownload/wicket-ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/exceldownload/wicket-ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/fullcalendar/applib/lombok.processor b/extensions/vw/fullcalendar/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/fullcalendar/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/fullcalendar/lombok.processor b/extensions/vw/fullcalendar/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/fullcalendar/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/fullcalendar/wicket/integration/lombok.processor b/extensions/vw/fullcalendar/wicket/integration/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/fullcalendar/wicket/integration/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/fullcalendar/wicket/lombok.processor b/extensions/vw/fullcalendar/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/fullcalendar/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/fullcalendar/wicket/ui/lombok.processor b/extensions/vw/fullcalendar/wicket/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/fullcalendar/wicket/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/applib/lombok.processor b/extensions/vw/pdfjs/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/fixtures/lombok.processor b/extensions/vw/pdfjs/fixtures/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/fixtures/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/lombok.processor b/extensions/vw/pdfjs/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/metamodel/lombok.processor b/extensions/vw/pdfjs/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/wicket/integration/lombok.processor b/extensions/vw/pdfjs/wicket/integration/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/wicket/integration/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/wicket/lombok.processor b/extensions/vw/pdfjs/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/pdfjs/wicket/ui/lombok.processor b/extensions/vw/pdfjs/wicket/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/pdfjs/wicket/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/sse/applib/lombok.processor b/extensions/vw/sse/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/sse/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/sse/lombok.processor b/extensions/vw/sse/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/sse/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/sse/metamodel/lombok.processor b/extensions/vw/sse/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/sse/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/extensions/vw/sse/wicket/lombok.processor b/extensions/vw/sse/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/extensions/vw/sse/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/clients/kroviz/lombok.processor b/incubator/clients/kroviz/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/clients/kroviz/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/core/jsr303/lombok.processor b/incubator/core/jsr303/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/core/jsr303/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/extensions/core/commandreplay/lombok.processor b/incubator/extensions/core/commandreplay/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/extensions/core/commandreplay/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/extensions/core/commandreplay/primary/lombok.processor b/incubator/extensions/core/commandreplay/primary/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/extensions/core/commandreplay/primary/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/extensions/core/commandreplay/secondary/lombok.processor b/incubator/extensions/core/commandreplay/secondary/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/extensions/core/commandreplay/secondary/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/lombok.processor b/incubator/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/graphql/applib/lombok.processor b/incubator/viewers/graphql/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/graphql/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/graphql/lombok.processor b/incubator/viewers/graphql/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/graphql/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/graphql/model/lombok.processor b/incubator/viewers/graphql/model/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/graphql/model/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/graphql/test/lombok.processor b/incubator/viewers/graphql/test/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/graphql/test/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/graphql/viewer/lombok.processor b/incubator/viewers/graphql/viewer/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/graphql/viewer/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/javafx/lombok.processor b/incubator/viewers/javafx/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/javafx/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/javafx/model/lombok.processor b/incubator/viewers/javafx/model/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/javafx/model/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/javafx/ui/lombok.processor b/incubator/viewers/javafx/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/javafx/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/javafx/viewer/lombok.processor b/incubator/viewers/javafx/viewer/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/javafx/viewer/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/vaadin/lombok.processor b/incubator/viewers/vaadin/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/vaadin/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/vaadin/model/lombok.processor b/incubator/viewers/vaadin/model/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/vaadin/model/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/vaadin/ui/lombok.processor b/incubator/viewers/vaadin/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/vaadin/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/incubator/viewers/vaadin/viewer/lombok.processor b/incubator/viewers/vaadin/viewer/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/incubator/viewers/vaadin/viewer/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/lombok.processor b/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/mavendeps/lombok.processor b/mavendeps/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/mavendeps/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/mavendeps/webapp/lombok.processor b/mavendeps/webapp/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/mavendeps/webapp/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/commons/lombok.processor b/persistence/commons/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/commons/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/applib/lombok.processor b/persistence/jdo/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/datanucleus/lombok.processor b/persistence/jdo/datanucleus/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/datanucleus/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/integration/lombok.processor b/persistence/jdo/integration/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/integration/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/lombok.processor b/persistence/jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/metamodel/lombok.processor b/persistence/jdo/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/provider/lombok.processor b/persistence/jdo/provider/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/provider/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jdo/spring/lombok.processor b/persistence/jdo/spring/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jdo/spring/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jpa/applib/lombok.processor b/persistence/jpa/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jpa/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jpa/eclipselink/lombok.processor b/persistence/jpa/eclipselink/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jpa/eclipselink/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jpa/integration/lombok.processor b/persistence/jpa/integration/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jpa/integration/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jpa/lombok.processor b/persistence/jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/persistence/jpa/metamodel/lombok.processor b/persistence/jpa/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/persistence/jpa/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/incubating/lombok.processor b/regressiontests/incubating/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/incubating/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/lombok.processor b/regressiontests/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-bootstrapping/lombok.processor b/regressiontests/stable-bootstrapping/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-bootstrapping/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-cmdexecauditsess/generic/lombok.processor b/regressiontests/stable-cmdexecauditsess/generic/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-cmdexecauditsess/generic/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-cmdexecauditsess/lombok.processor b/regressiontests/stable-cmdexecauditsess/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-cmdexecauditsess/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-cmdexecauditsess/persistence-jdo/lombok.processor b/regressiontests/stable-cmdexecauditsess/persistence-jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-cmdexecauditsess/persistence-jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-cmdexecauditsess/persistence-jpa/lombok.processor b/regressiontests/stable-cmdexecauditsess/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-cmdexecauditsess/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-config/lombok.processor b/regressiontests/stable-config/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-config/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-core-wrapperfactory/lombok.processor b/regressiontests/stable-core-wrapperfactory/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-core-wrapperfactory/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-cucumber/lombok.processor b/regressiontests/stable-cucumber/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-cucumber/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-domainmodel/lombok.processor b/regressiontests/stable-domainmodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-domainmodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-eventhandling/lombok.processor b/regressiontests/stable-eventhandling/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-eventhandling/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-factory/lombok.processor b/regressiontests/stable-factory/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-factory/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-interact/lombok.processor b/regressiontests/stable-interact/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-interact/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-layouts/lombok.processor b/regressiontests/stable-layouts/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-layouts/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-persistence-jdo/lombok.processor b/regressiontests/stable-persistence-jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-persistence-jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-persistence-jpa/lombok.processor b/regressiontests/stable-persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-publishing-jpa/lombok.processor b/regressiontests/stable-publishing-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-publishing-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-rest/lombok.processor b/regressiontests/stable-rest/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-rest/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-value/lombok.processor b/regressiontests/stable-value/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-value/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-viewers-common/lombok.processor b/regressiontests/stable-viewers-common/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-viewers-common/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-viewers-jdo/lombok.processor b/regressiontests/stable-viewers-jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-viewers-jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable-viewers-jpa/lombok.processor b/regressiontests/stable-viewers-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable-viewers-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/regressiontests/stable/lombok.processor b/regressiontests/stable/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/regressiontests/stable/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/security/bypass/lombok.processor b/security/bypass/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/security/bypass/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/security/keycloak/lombok.processor b/security/keycloak/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/security/keycloak/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/security/shiro/lombok.processor b/security/shiro/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/security/shiro/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/security/spring/lombok.processor b/security/spring/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/security/spring/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/starters/lombok.processor b/starters/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/starters/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/supplemental-model/lombok.processor b/supplemental-model/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/supplemental-model/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/archtestsupport/applib/lombok.processor b/testing/archtestsupport/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/archtestsupport/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/archtestsupport/lombok.processor b/testing/archtestsupport/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/archtestsupport/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/fakedata/applib/lombok.processor b/testing/fakedata/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/fakedata/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/fakedata/fixtures/lombok.processor b/testing/fakedata/fixtures/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/fakedata/fixtures/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/fakedata/integtests/lombok.processor b/testing/fakedata/integtests/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/fakedata/integtests/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/fakedata/lombok.processor b/testing/fakedata/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/fakedata/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/fixtures/applib/lombok.processor b/testing/fixtures/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/fixtures/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/fixtures/lombok.processor b/testing/fixtures/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/fixtures/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/h2console/lombok.processor b/testing/h2console/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/h2console/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/h2console/ui/lombok.processor b/testing/h2console/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/h2console/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/hsqldbmgr/lombok.processor b/testing/hsqldbmgr/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/hsqldbmgr/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/hsqldbmgr/ui/lombok.processor b/testing/hsqldbmgr/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/hsqldbmgr/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/integtestsupport/applib/lombok.processor b/testing/integtestsupport/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/integtestsupport/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/integtestsupport/lombok.processor b/testing/integtestsupport/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/integtestsupport/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/lombok.processor b/testing/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/specsupport/applib/lombok.processor b/testing/specsupport/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/specsupport/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/specsupport/lombok.processor b/testing/specsupport/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/specsupport/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/unittestsupport/applib/lombok.processor b/testing/unittestsupport/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/unittestsupport/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/testing/unittestsupport/lombok.processor b/testing/unittestsupport/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/testing/unittestsupport/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/c4modeling/lombok.processor b/tooling/c4modeling/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/c4modeling/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/cli/lombok.processor b/tooling/cli/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/cli/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/java2adoc/lombok.processor b/tooling/java2adoc/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/java2adoc/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/javamodel/lombok.processor b/tooling/javamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/javamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/lombok.processor b/tooling/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/metaprog/lombok.processor b/tooling/metaprog/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/metaprog/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/model4adoc/lombok.processor b/tooling/model4adoc/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/model4adoc/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/tooling/projectmodel/lombok.processor b/tooling/projectmodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/tooling/projectmodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/applib/lombok.processor b/valuetypes/asciidoc/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/lombok.processor b/valuetypes/asciidoc/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/metamodel/lombok.processor b/valuetypes/asciidoc/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/persistence-jdo/lombok.processor b/valuetypes/asciidoc/persistence-jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/persistence-jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/persistence-jpa/lombok.processor b/valuetypes/asciidoc/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/ui/lombok.processor b/valuetypes/asciidoc/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/ui/vaadin/lombok.processor b/valuetypes/asciidoc/ui/vaadin/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/ui/vaadin/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/asciidoc/ui/wicket/lombok.processor b/valuetypes/asciidoc/ui/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/asciidoc/ui/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/jodatime/applib/lombok.processor b/valuetypes/jodatime/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/jodatime/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/jodatime/integration/lombok.processor b/valuetypes/jodatime/integration/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/jodatime/integration/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/jodatime/lombok.processor b/valuetypes/jodatime/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/jodatime/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/lombok.processor b/valuetypes/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/applib/lombok.processor b/valuetypes/markdown/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/lombok.processor b/valuetypes/markdown/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/metamodel/lombok.processor b/valuetypes/markdown/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/persistence-jdo/lombok.processor b/valuetypes/markdown/persistence-jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/persistence-jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/persistence-jpa/lombok.processor b/valuetypes/markdown/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/ui/lombok.processor b/valuetypes/markdown/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/markdown/ui/wicket/lombok.processor b/valuetypes/markdown/ui/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/markdown/ui/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/applib/lombok.processor b/valuetypes/vega/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/lombok.processor b/valuetypes/vega/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/metamodel/lombok.processor b/valuetypes/vega/metamodel/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/metamodel/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/persistence-jdo/lombok.processor b/valuetypes/vega/persistence-jdo/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/persistence-jdo/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/persistence-jpa/lombok.processor b/valuetypes/vega/persistence-jpa/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/persistence-jpa/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/ui/lombok.processor b/valuetypes/vega/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/ui/vaadin/lombok.processor b/valuetypes/vega/ui/vaadin/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/ui/vaadin/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/valuetypes/vega/ui/wicket/lombok.processor b/valuetypes/vega/ui/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/valuetypes/vega/ui/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/commons/applib/lombok.processor b/viewers/commons/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/commons/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/commons/lombok.processor b/viewers/commons/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/commons/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/commons/model/lombok.processor b/viewers/commons/model/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/commons/model/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/commons/prism/lombok.processor b/viewers/commons/prism/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/commons/prism/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/commons/services/lombok.processor b/viewers/commons/services/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/commons/services/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/applib/lombok.processor b/viewers/restfulobjects/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/client/lombok.processor b/viewers/restfulobjects/client/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/client/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/jaxrs-resteasy/lombok.processor b/viewers/restfulobjects/jaxrs-resteasy/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/jaxrs-resteasy/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/lombok.processor b/viewers/restfulobjects/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/rendering/lombok.processor b/viewers/restfulobjects/rendering/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/rendering/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/testing/lombok.processor b/viewers/restfulobjects/testing/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/testing/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/restfulobjects/viewer/lombok.processor b/viewers/restfulobjects/viewer/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/restfulobjects/viewer/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/wicket/applib/lombok.processor b/viewers/wicket/applib/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/wicket/applib/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/wicket/graceful/lombok.processor b/viewers/wicket/graceful/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/wicket/graceful/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/wicket/lombok.processor b/viewers/wicket/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/wicket/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/wicket/model/lombok.processor b/viewers/wicket/model/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/wicket/model/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/wicket/ui/lombok.processor b/viewers/wicket/ui/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/wicket/ui/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+
diff --git a/viewers/wicket/viewer/lombok.processor b/viewers/wicket/viewer/lombok.processor
new file mode 100644
index 0000000000..d5ead5b02b
--- /dev/null
+++ b/viewers/wicket/viewer/lombok.processor
@@ -0,0 +1,10 @@
+The presence of this file activates a profile (defined in bom/pom.xml) that configures maven-compiler-plugin to run the lombok annotation processor.
+
+This is a workaround; the compiler ought to pick up all available processors on the classpath anyway; unknown why it does not, but is probably a badly formed pom.xml somewhere causing dependencies to be ignored.
+
+This file has only been added to the modules where it was found to be required.
+
+The one place where this file is _not_ required is with the JDO modules that declare @PersistenceCapable entities.
+Such modules need both lombok AND the DN annotation processor (datanucleus-jdo-query) that generates the Qxxx query classes.
+For some reason, with these JDO modules, the default behaviour (picking up all available processors) does seem to work.
+