问题描述
我们刚刚将JBoss从6.1.0升级到Wildfly 10.1，并对模块和工件版本等进行了各种关联的升级.在一个模块中，这导致我们的cobertura编译失败并出现编译器错误.我在使用Maven的Hibernate元模型生成中发现了 IllegalStateException ，并升级到了maven-编译器插件3.6.0(来自3.1).这似乎解决了我的问题，但仅在本地范围内.我可以为cobertura编译模块，但事实证明这会引起新的问题.
We just upgraded our JBoss from 6.1.0 to Wildfly 10.1, and made a variety of associated upgrades to modules and artifact versions and so on. In one module this caused our cobertura compiles to fail with a compiler error. I found IllegalStateException in Hibernate metamodel generation with maven and upgraded to maven-compiler-plugin 3.6.0 (from 3.1). This seemed to resolve my problem, but only on a local basis. I can compile the module for cobertura, but it turns out to cause a new problem.
此模块的一些注释生成的源由另一个模块使用，但未找到类文件.发生了什么变化? Generated-sources目录包含Java文件，但未编译这些类.
Some of the annotation-generated sources for this module are used by another module, and the class files aren't found. What changed? The generated-sources directory contains the java files, but the classes aren't compiled.
它看起来就像改变构建帮助程序阶段以从过程源生成源一样，但后来失败了.
It looked at one point like changing the build-helper phase to generate-sources from process-sources helped, but that failed subsequently.
由于3.1和3.6.0之间的更改，是否还需要更改其他内容? (我不熟悉如何处理注释-我只是Cobertura支持人员.)
Is there something else that needs to be changed because of changes between 3.1 and 3.6.0? (I'm not familiar with how to process annotations - I'm just the Cobertura support guy.)
pom文件:
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<description>The JPA entities for the Element Manager</description>
<artifactId>em-model</artifactId>
<groupId>com.myprod.em</groupId>
<parent>
<artifactId>em</artifactId>
<groupId>com.myprod</groupId>
<version>3.5.0.0.0-SNAPSHOT</version>
</parent>
<packaging>jar</packaging>
<build>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<executions>
<execution>
<phase>process-sources</phase>
<configuration>
<sources>
<source>${project.build.directory}/generated-sources/annotations</source>
</sources>
</configuration>
<goals>
<goal>add-source</goal>
</goals>
</execution>
</executions>
</plugin>
<plugin>
<artifactId>maven-jar-plugin</artifactId>
<groupId>org.apache.maven.plugins</groupId>
<configuration>
<finalName>em-model</finalName>
</configuration>
</plugin>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<compilerArgument>-proc:none</compilerArgument>
</configuration>
<executions>
<execution>
<id>run-annotation-processors-only</id>
<phase>generate-sources</phase>
<configuration>
<compilerArgument>-proc:only</compilerArgument>
</configuration>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
<dependencies>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-validator</artifactId>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-core</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.glassfish</groupId>
<artifactId>javax.el</artifactId>
<version>3.0.1-b08</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.ejb</groupId>
<artifactId>jboss-ejb-api_3.2_spec</artifactId>
<scope>provided</scope>
</dependency>
<!-- Since hibernate validator is used in unit tests,
these JBoss logging deps are needed -->
<dependency>
<groupId>org.jboss.slf4j</groupId>
<artifactId>slf4j-jboss-logmanager</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.jboss.logmanager</groupId>
<artifactId>jboss-logmanager</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-api</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.codehaus.jackson</groupId>
<artifactId>jackson-mapper-asl</artifactId>
<version>1.8.5</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-io</artifactId>
<version>1.3.2</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.myco.csp</groupId>
<artifactId>nrp_jpa</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.myco.cim</groupId>
<artifactId>cs_cim_jpa</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.hibernate</groupId>
<artifactId>hibernate-jpamodelgen</artifactId>
<version>1.0.0.Final</version>
<scope>provided</scope>
</dependency>
<!-- Test -->
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-all</artifactId>
</dependency>
<dependency>
<groupId>com.myco.logging</groupId>
<artifactId>logging-client</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>apache-log4j</groupId>
<artifactId>log4j</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.myprod.prodCommon</groupId>
<artifactId>unit-test-utils</artifactId>
<version>${project.version}</version>
<scope>test</scope>
</dependency>
</dependencies>
推荐答案
我通过从编译器插件中删除-proc:none编译器参数来解决此问题.目前，所有生成的源都没有被编译.使用3.1插件时，我必须拥有它，但使用3.6.0时，我则不需要.
I resolved this by removing the -proc:none compiler argument from the compiler plugin. With that present none of the generated sources were being compiled at all. With the 3.1 plugin I had to have that, but with 3.6.0 I can't.
我还尝试通过以下方法来实现答案 https://stackoverflow.com/a/35045416/4756238 compilerArg特定于默认编译阶段，但是没有编译生成的源.如果我不重用默认编译ID，则该构建可以工作并提供给我生成的类文件，但是它运行了两个编译阶段，-proc:none是一秒钟，这似乎是多余的.
I also tried to implement the answer https://stackoverflow.com/a/35045416/4756238 by making the compilerArg specific to the default-compile phase, but that didn't compile the generated sources. If I didn't reuse the default-compile id the build worked and gave me generated class files, but it ran two compile phases, with the -proc:none one second, which seemed redundant.
编译器的最后pom部分如下所示:
The final pom section for the compiler looks like this:
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<executions>
<execution>
<id>run-annotation-processors-only</id>
<phase>generate-sources</phase>
<configuration>
<compilerArgument>-proc:only</compilerArgument>
</configuration>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
</plugin>
这篇关于maven-compiler-plugin 3.6.0不会从注释中编译生成的源的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！