jira-importer

**[Matt Sicker](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jvz)** commented Oh that above useless error appears to be when a compile error is encountered in fork=true mode, the error message doesn't appear to propagate correctly.

**[Matt Sicker](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=jvz)** commented Double-problem caused the lack of error reporting: using forceJavacCompilerUse=true in the configuration prevented errors in an annotation processor from being surfaced. Switching that back to false surfaced...

**[Slawomir Jaranowski](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=slawekjaranowski)** commented Thanks for reporting. Please provide a simple project which can be used to reproduce your issue.

**[Eric Hubert](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ehubert)** commented It looks like we can close the issue as invalid. It all seems to be caused by a wrong/unintended configuration of the compiler plugin in the Maven...

**[Philippe De Neve](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=JIRAUSER306977)** commented Seems to be fixed with maven-compiler-plugin v3.14.0. However, there is then a warning: `JDK-8318913 workaround: patched module-info.class requires version from [23] to [23] on 1 JDK...

**[Tamas Cservenak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cstamas)** commented [Martin Desruisseaux](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=desruisseaux) ping

**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented I expect this will work exactly the same as for the classpath/modulepath: feed all jars of the annotationProcessorPaths together with the module-info to the locationManager and it'll...

**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented Depends on [Support --process-module-path](https://github.com/codehaus-plexus/plexus-compiler/issues/150) in plexus-compiler

**[Anand Beh](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=a248)** commented FYI for anyone else who happened across this issue, there is a temporary workaround using the maven-dependency-plugin and specifying the processor-module-path via a property: ```java org.apache.maven.plugins maven-dependency-plugin...

**[Gili](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=cowwoc)** commented Either the parameter name change or there is a typo in the title and description. I think you meant to refer to `\--processor-module-path` not `\--process-module-path`.