processor-plugin | Bookshelf plugin that allows defining custom processor

I'm currently working on a java project where I need to generate and compile JPA metamodel classes as part of the build. I did some research and found an answer here: Generate the JPA metamodel files using maven-processor-plugin - What is a convenient way for re-generation? that seems like a reasonable solution. The problem is, my project also contains some groovy classes that need to be compiled alongside the java. If I enable the maven-processor-plugin, the maven build will fail as soon as it encounters a java class that depends on a groovy class. Looking at the console output, I can see that maven-processor-plugin is running before the groovy compiler, so those groovy classes have not had a chance to be compiled.

Does anyone know if there is a good way to handle this? Is there some way to break the compilation process up into stages so that I can control what gets processed when?

Here is a snippet of my pom.xml:

I have a java module with JPA entities and persistence.xml and I want to generate metamodel. I tried two variants.

Variant 1

Please, help to exclude module-info file.

This is my code:

i am using spring boot and swagger to generate model and delegates using swagger first approach. The problem is that constraints such as @NotNull, @Size are placed on getter methods and not on the fields. Thats why i can pass random value for example to email field. Please help me solve this problem. Here is my pom.xml:

I am unable to build JPA2 projects after upgrading my JDK to 11 and getting errors, cannot find symbol. I checked and the package names have changed in 11. So, for instance:

Generated is no longer in:

I have code that uses maven-processor-plugin to have Hibernate generate some classes in folder src/main/generated of a Java project. I am preparing the migration of the project to Java 11, in the development environment as well as in the runtime environment.

Until now, everything worked fine with Hibernate 4.3.10.Final and Java 8. After installing JDK 11 and using Hibernate 5.4.4.Final, I've come across the infamous javax.annotation.Generated problem.

Since Hibernate 5.4.4.Final is supposed to be compatible with Java 9+, I was expecting the generated files to switch to javax.annotation.processing.Generated. Unfortunately, the old qualified name is the one that I can still see in those files, in the imports section. As a consequence, the compilation of generated files will fail.

Here is what I configured:

• maven-processor-plugin, with 11
• The target level in pom.xml, with 1.11
• The release in pom.xml, with 11
• In Eclipse, the Java compiler is using the '--release' option and set to compliance level "11".
• On the system, there's only one JDK installed: 11.0.4.

On further investigation, I have realized that the Context class in org.hibernate:hibernate-jpamodelgen:5.4.4.Final has this code:

I've been upgrading my app to use spring boot 2 and my views have not been rendering correctly. They content that should be hidden with the is no longer working. My methods and pages are still secured properly so it seems to be an issue with rendering the page. Also, isAuthenticated and isAnonymous don't work either.

I've tried changing to and my security tag to xmlns:sec="http://www.thymeleaf.org/extras/spring-security" from xmlns:sec="http://www.thymeleaf.org/thymeleaf-extras-springsecurity4"

SECURITY CONFIG

I'm getting the warning listed below from the maven-processor-plugin when used to process the Open JPA meta model for Java 8. My project actually builds, but is there a version of this for Java 8 that does not generate this warning? I don't see a Java 8 version of org.apache.openjpa.persistence.meta.AnnotationProcessor6.

warning: Supported source version 'RELEASE_6' from annotation processor 'org.apache.openjpa.persistence.meta.AnnotationProcessor6' less than -source '1.8'

Some context

I am creating a Spring Boot base code application that is in fact separated in three projects/modules:

springbase-core

contains:

• custom annotations
• custom exceptions
• custom generic Spring components
• model (entities)
• metamodels (generated by maven through the maven-processor-plugin)
• utils

depends on: nothing

springbase-data

contains:

• data related annotations
• services
• repositories
• data related util classes

depends on: springbase-core

springbase-web

• controllers
• form classes
• filters
• listeners
• interceptors
• JSPs
• JSP Tags
• etc.

depends on: springbase-data, springbase-core

The problem I am having is that if I have springbase-core in my Eclipse workspace, I'm not able to import metamodels in repository classes in springbase-data. If I remove the springbase-core project (where metamodels reisde) from my Eclipse workspace, it works.

I have also tried copying springbase-core-0.0.1-SNAPSHOT.jar from my .m2 repository, directly at the root of my project (and taking care of adding it in .classpath), and I was able to import metamodels.

When opening springbase-core-0.0.1-SNAPSHOT.jar with WinZip, I can see the metamodels. Building springbase-core with Maven also shows the generated metamodels under /target/metamodel as configured in my pom.xml.

Looks like a glitch between Eclipse and Maven.

Any thoughts?