You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by ah...@apache.org on 2023/03/04 08:53:08 UTC
[causeway] branch master updated: CAUSEWAY-3252: remove lombok.processor files
This is an automated email from the ASF dual-hosted git repository.
ahuber pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/causeway.git
The following commit(s) were added to refs/heads/master by this push:
new a448208e79 CAUSEWAY-3252: remove lombok.processor files
a448208e79 is described below
commit a448208e790d760efbe030bc0581d00d86a3317d
Author: Andi Huber <ah...@apache.org>
AuthorDate: Sat Mar 4 09:53:04 2023 +0100
CAUSEWAY-3252: remove lombok.processor files
---
antora/lombok.processor | 8 --------
api/applib/lombok.processor | 8 --------
api/schema/lombok.processor | 8 --------
bom/lombok.processor | 8 --------
bom/pom.xml | 6 +++---
commons/lombok.processor | 8 --------
core/codegen-bytebuddy/lombok.processor | 8 --------
core/interaction/lombok.processor | 8 --------
core/internaltestsupport/lombok.processor | 8 --------
core/lombok.processor | 8 --------
core/metamodel/lombok.processor | 8 --------
core/runtime/lombok.processor | 8 --------
core/runtimeservices/lombok.processor | 8 --------
core/security/lombok.processor | 8 --------
core/transaction/lombok.processor | 8 --------
core/webapp/lombok.processor | 8 --------
examples/demo/domain-tests/lombok.processor | 8 --------
examples/demo/domain/lombok.processor | 8 --------
examples/demo/javafx/lombok.processor | 8 --------
examples/demo/lombok.processor | 8 --------
examples/demo/vaadin/lombok.processor | 8 --------
examples/demo/web/lombok.processor | 8 --------
examples/demo/wicket/common/lombok.processor | 8 --------
examples/demo/wicket/jdo/lombok.processor | 8 --------
examples/demo/wicket/jpa-and-graphql/lombok.processor | 8 --------
examples/demo/wicket/jpa/lombok.processor | 8 --------
extensions/core/commandlog/applib/lombok.processor | 8 --------
extensions/core/commandlog/lombok.processor | 8 --------
extensions/core/commandlog/persistence-jpa/lombok.processor | 8 --------
extensions/core/docgen/lombok.processor | 8 --------
extensions/core/excel/applib/lombok.processor | 8 --------
extensions/core/excel/fixture/lombok.processor | 8 --------
extensions/core/excel/integtests/lombok.processor | 8 --------
extensions/core/excel/lombok.processor | 8 --------
extensions/core/excel/testing/lombok.processor | 8 --------
extensions/core/executionlog/applib/lombok.processor | 8 --------
extensions/core/executionlog/lombok.processor | 8 --------
extensions/core/executionlog/persistence-jpa/lombok.processor | 8 --------
extensions/core/executionoutbox/applib/lombok.processor | 8 --------
extensions/core/executionoutbox/lombok.processor | 8 --------
extensions/core/executionoutbox/persistence-jpa/lombok.processor | 8 --------
extensions/core/executionoutbox/restclient/lombok.processor | 8 --------
extensions/core/executionrepublisher/applib/lombok.processor | 8 --------
extensions/core/executionrepublisher/lombok.processor | 8 --------
extensions/core/flyway/impl/lombok.processor | 8 --------
extensions/core/flyway/lombok.processor | 8 --------
extensions/lombok.processor | 8 --------
extensions/security/audittrail/applib/lombok.processor | 8 --------
extensions/security/audittrail/lombok.processor | 8 --------
extensions/security/audittrail/persistence-jpa/lombok.processor | 8 --------
extensions/security/secman/applib/lombok.processor | 8 --------
extensions/security/secman/delegated-shiro/lombok.processor | 8 --------
.../security/secman/delegated-springoauth2/lombok.processor | 8 --------
extensions/security/secman/encryption-jbcrypt/lombok.processor | 8 --------
extensions/security/secman/encryption-spring/lombok.processor | 8 --------
extensions/security/secman/integration/lombok.processor | 8 --------
extensions/security/secman/lombok.processor | 8 --------
extensions/security/secman/persistence-jpa/lombok.processor | 8 --------
extensions/security/sessionlog/applib/lombok.processor | 8 --------
extensions/security/sessionlog/lombok.processor | 8 --------
extensions/security/sessionlog/persistence-jpa/lombok.processor | 8 --------
extensions/security/shiro-realm-ldap/impl/lombok.processor | 8 --------
extensions/security/shiro-realm-ldap/lombok.processor | 8 --------
extensions/security/spring-oauth2/lombok.processor | 8 --------
extensions/vro/cors/impl/lombok.processor | 8 --------
extensions/vro/cors/lombok.processor | 8 --------
extensions/vw/exceldownload/lombok.processor | 8 --------
extensions/vw/exceldownload/wicket-ui/lombok.processor | 8 --------
extensions/vw/fullcalendar/applib/lombok.processor | 8 --------
extensions/vw/fullcalendar/lombok.processor | 8 --------
extensions/vw/fullcalendar/wicket/integration/lombok.processor | 8 --------
extensions/vw/fullcalendar/wicket/lombok.processor | 8 --------
extensions/vw/fullcalendar/wicket/ui/lombok.processor | 8 --------
extensions/vw/pdfjs/applib/lombok.processor | 8 --------
extensions/vw/pdfjs/fixtures/lombok.processor | 8 --------
extensions/vw/pdfjs/lombok.processor | 8 --------
extensions/vw/pdfjs/metamodel/lombok.processor | 8 --------
extensions/vw/pdfjs/wicket/integration/lombok.processor | 8 --------
extensions/vw/pdfjs/wicket/lombok.processor | 8 --------
extensions/vw/pdfjs/wicket/ui/lombok.processor | 8 --------
extensions/vw/sse/applib/lombok.processor | 8 --------
extensions/vw/sse/lombok.processor | 8 --------
extensions/vw/sse/metamodel/lombok.processor | 8 --------
extensions/vw/sse/wicket/lombok.processor | 8 --------
incubator/clients/kroviz/lombok.processor | 8 --------
incubator/core/jsr303/lombok.processor | 8 --------
incubator/extensions/core/commandreplay/lombok.processor | 8 --------
incubator/extensions/core/commandreplay/primary/lombok.processor | 8 --------
.../extensions/core/commandreplay/secondary/lombok.processor | 8 --------
incubator/lombok.processor | 8 --------
incubator/viewers/graphql/applib/lombok.processor | 8 --------
incubator/viewers/graphql/lombok.processor | 8 --------
incubator/viewers/graphql/model/lombok.processor | 8 --------
incubator/viewers/graphql/test/lombok.processor | 8 --------
incubator/viewers/graphql/viewer/lombok.processor | 8 --------
incubator/viewers/javafx/lombok.processor | 8 --------
incubator/viewers/javafx/model/lombok.processor | 8 --------
incubator/viewers/javafx/ui/lombok.processor | 8 --------
incubator/viewers/javafx/viewer/lombok.processor | 8 --------
incubator/viewers/vaadin/lombok.processor | 8 --------
incubator/viewers/vaadin/model/lombok.processor | 8 --------
incubator/viewers/vaadin/ui/lombok.processor | 8 --------
incubator/viewers/vaadin/viewer/lombok.processor | 8 --------
lombok.processor | 8 --------
mavendeps/lombok.processor | 8 --------
mavendeps/webapp/lombok.processor | 8 --------
persistence/commons/lombok.processor | 8 --------
persistence/jdo/applib/lombok.processor | 8 --------
persistence/jdo/datanucleus/lombok.processor | 8 --------
persistence/jdo/integration/lombok.processor | 8 --------
persistence/jdo/lombok.processor | 8 --------
persistence/jdo/metamodel/lombok.processor | 8 --------
persistence/jdo/provider/lombok.processor | 8 --------
persistence/jdo/spring/lombok.processor | 8 --------
persistence/jpa/applib/lombok.processor | 8 --------
persistence/jpa/eclipselink/lombok.processor | 8 --------
persistence/jpa/integration/lombok.processor | 8 --------
persistence/jpa/lombok.processor | 8 --------
persistence/jpa/metamodel/lombok.processor | 8 --------
regressiontests/incubating/lombok.processor | 8 --------
regressiontests/lombok.processor | 8 --------
regressiontests/stable-bootstrapping/lombok.processor | 8 --------
regressiontests/stable-cmdexecauditsess/generic/lombok.processor | 8 --------
regressiontests/stable-cmdexecauditsess/lombok.processor | 8 --------
.../stable-cmdexecauditsess/persistence-jdo/lombok.processor | 8 --------
.../stable-cmdexecauditsess/persistence-jpa/lombok.processor | 8 --------
regressiontests/stable-config/lombok.processor | 8 --------
regressiontests/stable-core-wrapperfactory/lombok.processor | 8 --------
regressiontests/stable-cucumber/lombok.processor | 8 --------
regressiontests/stable-domainmodel/lombok.processor | 8 --------
regressiontests/stable-eventhandling/lombok.processor | 8 --------
regressiontests/stable-factory/lombok.processor | 8 --------
regressiontests/stable-interact/lombok.processor | 8 --------
regressiontests/stable-layouts/lombok.processor | 8 --------
regressiontests/stable-persistence-jdo/lombok.processor | 8 --------
regressiontests/stable-persistence-jpa/lombok.processor | 8 --------
regressiontests/stable-publishing-jpa/lombok.processor | 8 --------
regressiontests/stable-rest/lombok.processor | 8 --------
regressiontests/stable-value/lombok.processor | 8 --------
regressiontests/stable-viewers-common/lombok.processor | 8 --------
regressiontests/stable-viewers-jdo/lombok.processor | 8 --------
regressiontests/stable-viewers-jpa/lombok.processor | 8 --------
regressiontests/stable/lombok.processor | 8 --------
security/bypass/lombok.processor | 8 --------
security/keycloak/lombok.processor | 8 --------
security/shiro/lombok.processor | 8 --------
security/spring/lombok.processor | 8 --------
starters/lombok.processor | 8 --------
supplemental-model/lombok.processor | 8 --------
testing/archtestsupport/applib/lombok.processor | 8 --------
testing/archtestsupport/lombok.processor | 8 --------
testing/fakedata/applib/lombok.processor | 8 --------
testing/fakedata/fixtures/lombok.processor | 8 --------
testing/fakedata/integtests/lombok.processor | 8 --------
testing/fakedata/lombok.processor | 8 --------
testing/fixtures/applib/lombok.processor | 8 --------
testing/fixtures/lombok.processor | 8 --------
testing/h2console/lombok.processor | 8 --------
testing/h2console/ui/lombok.processor | 8 --------
testing/hsqldbmgr/lombok.processor | 8 --------
testing/hsqldbmgr/ui/lombok.processor | 8 --------
testing/integtestsupport/applib/lombok.processor | 8 --------
testing/integtestsupport/lombok.processor | 8 --------
testing/lombok.processor | 8 --------
testing/specsupport/applib/lombok.processor | 8 --------
testing/specsupport/lombok.processor | 8 --------
testing/unittestsupport/applib/lombok.processor | 8 --------
testing/unittestsupport/lombok.processor | 8 --------
tooling/c4modeling/lombok.processor | 8 --------
tooling/cli/lombok.processor | 8 --------
tooling/java2adoc/lombok.processor | 8 --------
tooling/javamodel/lombok.processor | 8 --------
tooling/lombok.processor | 8 --------
tooling/metaprog/lombok.processor | 8 --------
tooling/model4adoc/lombok.processor | 8 --------
tooling/projectmodel/lombok.processor | 8 --------
valuetypes/asciidoc/applib/lombok.processor | 8 --------
valuetypes/asciidoc/lombok.processor | 8 --------
valuetypes/asciidoc/metamodel/lombok.processor | 8 --------
valuetypes/asciidoc/persistence-jdo/lombok.processor | 8 --------
valuetypes/asciidoc/persistence-jpa/lombok.processor | 8 --------
valuetypes/asciidoc/ui/lombok.processor | 8 --------
valuetypes/asciidoc/ui/vaadin/lombok.processor | 8 --------
valuetypes/asciidoc/ui/wicket/lombok.processor | 8 --------
valuetypes/jodatime/applib/lombok.processor | 8 --------
valuetypes/jodatime/integration/lombok.processor | 8 --------
valuetypes/jodatime/lombok.processor | 8 --------
valuetypes/lombok.processor | 8 --------
valuetypes/markdown/applib/lombok.processor | 8 --------
valuetypes/markdown/lombok.processor | 8 --------
valuetypes/markdown/metamodel/lombok.processor | 8 --------
valuetypes/markdown/persistence-jdo/lombok.processor | 8 --------
valuetypes/markdown/persistence-jpa/lombok.processor | 8 --------
valuetypes/markdown/ui/lombok.processor | 8 --------
valuetypes/markdown/ui/wicket/lombok.processor | 8 --------
valuetypes/vega/applib/lombok.processor | 8 --------
valuetypes/vega/lombok.processor | 8 --------
valuetypes/vega/metamodel/lombok.processor | 8 --------
valuetypes/vega/persistence-jdo/lombok.processor | 8 --------
valuetypes/vega/persistence-jpa/lombok.processor | 8 --------
valuetypes/vega/ui/lombok.processor | 8 --------
valuetypes/vega/ui/vaadin/lombok.processor | 8 --------
valuetypes/vega/ui/wicket/lombok.processor | 8 --------
viewers/commons/applib/lombok.processor | 8 --------
viewers/commons/lombok.processor | 8 --------
viewers/commons/model/lombok.processor | 8 --------
viewers/commons/prism/lombok.processor | 8 --------
viewers/commons/services/lombok.processor | 8 --------
viewers/restfulobjects/applib/lombok.processor | 8 --------
viewers/restfulobjects/client/lombok.processor | 8 --------
viewers/restfulobjects/jaxrs-resteasy/lombok.processor | 8 --------
viewers/restfulobjects/lombok.processor | 8 --------
viewers/restfulobjects/rendering/lombok.processor | 8 --------
viewers/restfulobjects/testing/lombok.processor | 8 --------
viewers/restfulobjects/viewer/lombok.processor | 8 --------
viewers/wicket/applib/lombok.processor | 8 --------
viewers/wicket/graceful/lombok.processor | 8 --------
viewers/wicket/lombok.processor | 8 --------
viewers/wicket/model/lombok.processor | 8 --------
viewers/wicket/ui/lombok.processor | 8 --------
viewers/wicket/viewer/lombok.processor | 8 --------
221 files changed, 3 insertions(+), 1763 deletions(-)
diff --git a/antora/lombok.processor b/antora/lombok.processor
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/antora/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/api/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/api/schema/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/bom/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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 7170f87ea0..23129a2576 100644
--- a/bom/pom.xml
+++ b/bom/pom.xml
@@ -2234,10 +2234,10 @@ It is therefore a copy of org.apache:apache, with customisations clearly identif
<showWarnings>true</showWarnings>
<parameters>true</parameters>
<annotationProcessorPaths>
- <!-- this is a workaround, lombok's annotation processor should be picked up implicitly, but yet is not.
+ <!-- this is a workaround
- Details:
- This is a workaround; the compiler ought to pick up all available processors on the classpath.
+ Details: The maven compiler plugin ought to pick up all available processors on the classpath.
+ In effect Lombok's annotation processor should be picked up implicitly, but yet is not
Also Note: Presence of file 'logging-dn-enhance.properties' activates a profile (defined blow),
that configures maven-compiler-plugin to run all annotation processors required
diff --git a/commons/lombok.processor b/commons/lombok.processor
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/commons/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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/lombok.processor b/core/codegen-bytebuddy/lombok.processor
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/codegen-bytebuddy/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/interaction/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/internaltestsupport/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/runtime/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/runtimeservices/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/security/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/transaction/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/core/webapp/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/domain-tests/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/domain/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/javafx/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/vaadin/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/web/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/wicket/common/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/wicket/jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/wicket/jpa-and-graphql/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/examples/demo/wicket/jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/commandlog/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/commandlog/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/commandlog/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/docgen/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/excel/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/excel/fixture/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/excel/integtests/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/excel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/excel/testing/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionlog/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionlog/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionlog/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionoutbox/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionoutbox/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionoutbox/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionoutbox/restclient/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionrepublisher/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/executionrepublisher/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/flyway/impl/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/core/flyway/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/audittrail/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/audittrail/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/audittrail/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/delegated-shiro/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/delegated-springoauth2/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/encryption-jbcrypt/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/encryption-spring/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/integration/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/secman/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/sessionlog/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/sessionlog/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/sessionlog/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/shiro-realm-ldap/impl/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/shiro-realm-ldap/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/security/spring-oauth2/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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/impl/lombok.processor b/extensions/vro/cors/impl/lombok.processor
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vro/cors/impl/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vro/cors/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/exceldownload/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/exceldownload/wicket-ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/fullcalendar/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/fullcalendar/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/fullcalendar/wicket/integration/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/fullcalendar/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/fullcalendar/wicket/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/fixtures/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/wicket/integration/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/pdfjs/wicket/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/sse/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/sse/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/sse/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/extensions/vw/sse/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/clients/kroviz/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/core/jsr303/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/extensions/core/commandreplay/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/extensions/core/commandreplay/primary/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/extensions/core/commandreplay/secondary/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/graphql/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/graphql/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/graphql/model/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/graphql/test/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/graphql/viewer/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/javafx/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/javafx/model/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/javafx/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/javafx/viewer/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/vaadin/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/vaadin/model/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/vaadin/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/incubator/viewers/vaadin/viewer/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/mavendeps/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/mavendeps/webapp/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/commons/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/datanucleus/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/integration/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/provider/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jdo/spring/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jpa/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jpa/eclipselink/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jpa/integration/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/persistence/jpa/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/incubating/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-bootstrapping/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-cmdexecauditsess/generic/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-cmdexecauditsess/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-cmdexecauditsess/persistence-jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-cmdexecauditsess/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-config/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-core-wrapperfactory/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-cucumber/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-domainmodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-eventhandling/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-factory/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-interact/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-layouts/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-persistence-jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-publishing-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-rest/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-value/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-viewers-common/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-viewers-jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable-viewers-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/regressiontests/stable/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/security/bypass/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/security/keycloak/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/security/shiro/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/security/spring/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/starters/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/supplemental-model/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/archtestsupport/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/archtestsupport/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/fakedata/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/fakedata/fixtures/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/fakedata/integtests/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/fakedata/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/fixtures/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/fixtures/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/h2console/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/h2console/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/hsqldbmgr/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/hsqldbmgr/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/integtestsupport/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/integtestsupport/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/specsupport/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/specsupport/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/unittestsupport/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/testing/unittestsupport/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/c4modeling/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/cli/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/java2adoc/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/javamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/metaprog/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/model4adoc/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/tooling/projectmodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/persistence-jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/ui/vaadin/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/asciidoc/ui/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/jodatime/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/jodatime/integration/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/jodatime/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/persistence-jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/markdown/ui/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/metamodel/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/persistence-jdo/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/persistence-jpa/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/ui/vaadin/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/valuetypes/vega/ui/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/commons/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/commons/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/commons/model/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/commons/prism/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/commons/services/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/client/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/jaxrs-resteasy/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/rendering/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/testing/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/restfulobjects/viewer/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/wicket/applib/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/wicket/graceful/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/wicket/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/wicket/model/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/wicket/ui/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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
deleted file mode 100644
index fddaf8b3a7..0000000000
--- a/viewers/wicket/viewer/lombok.processor
+++ /dev/null
@@ -1,8 +0,0 @@
-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.
-
-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.
-