是否可以在同一 Maven 项目的源文件中动态生成和引用类?
在 Maven Build 中,我使用字节代码生成库 (Byte Buddy) 动态生成一些 Java 类型。当然,这些类文件没有相应的源文件。以这种方式只会生成几个类。这个项目的大部分代码将是Java源代码。理想情况下,Java源代码将以静态方式引用生成的类型,而不是使用反射或运行时代码生成,这意味着类需要位于javac的编译类路径上。我是否可以在同一 Maven 项目的编译类路径上获取生成的类,即没有单独的 Maven 项目和工件来保存包含源代码的 Maven 项目引用的生成的字节代码?
更新:我已经尝试过将生成的类直接放入Maven构建生命周期的早期,但似乎不在类路径上。生成的类型无法由 Maven 编译器插件或 IDE 解析。我还尝试使用Build Helper Maven插件在包含生成的类下添加一个额外的资源目录,然后将其自动复制到.此配置表现出相同的问题。target/classes
project.build.outputDirectory
target
target/classes
更新:我在GitHub上创建了一个完整的公共存储库:https://github.com/mches/so-42376851
以下是我想要的项目的Maven POM,我希望具有引用字节码增强类的静态类:
<?xml version="1.0" encoding="UTF-8"?>
<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>
<parent>
<groupId>demo</groupId>
<artifactId>demo</artifactId>
<version>1.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
<artifactId>demo-enhanced</artifactId>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<executions>
<execution>
<phase>generate-resources</phase>
<goals>
<goal>unpack</goal>
</goals>
<configuration>
<artifactItems>
<artifactItem>
<groupId>demo</groupId>
<artifactId>demo-original</artifactId>
<version>${project.version}</version>
<overWrite>true</overWrite>
<outputDirectory>${project.build.outputDirectory}</outputDirectory>
<includes>**/*.class</includes>
<excludes>META-INF/</excludes>
</artifactItem>
</artifactItems>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>net.bytebuddy</groupId>
<artifactId>byte-buddy-maven-plugin</artifactId>
<executions>
<execution>
<phase>process-resources</phase>
<goals>
<goal>transform</goal>
</goals>
<configuration>
<initialization>
<entryPoint>net.bytebuddy.test.SimpleEntryPoint</entryPoint>
<groupId>demo</groupId>
<artifactId>demo-transformer</artifactId>
</initialization>
<transformations>
<transformation>
<plugin>net.bytebuddy.test.SimplePlugin</plugin>
<groupId>demo</groupId>
<artifactId>demo-transformer</artifactId>
</transformation>
</transformations>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>
这是父 POM:
<?xml version="1.0" encoding="UTF-8"?>
<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>
<groupId>demo</groupId>
<artifactId>demo</artifactId>
<version>1.0-SNAPSHOT</version>
<packaging>pom</packaging>
<modules>
<module>demo-original</module>
<module>demo-transformer</module>
<module>demo-enhanced</module>
</modules>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
<byte-buddy.version>1.6.9</byte-buddy.version>
</properties>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>net.bytebuddy</groupId>
<artifactId>byte-buddy</artifactId>
<version>${byte-buddy.version}</version>
</dependency>
<dependency>
<groupId>demo</groupId>
<artifactId>demo-original</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>demo</groupId>
<artifactId>demo-transformer</artifactId>
<version>${project.version}</version>
</dependency>
<dependency>
<groupId>demo</groupId>
<artifactId>demo-enhanced</artifactId>
<version>${project.version}</version>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<pluginManagement>
<plugins>
<plugin>
<groupId>net.bytebuddy</groupId>
<artifactId>byte-buddy-maven-plugin</artifactId>
<version>${byte-buddy.version}</version>
</plugin>
</plugins>
</pluginManagement>
</build>
</project>
foo/Bar.java(原始来源):
package foo;
public class Bar {
}
net/bytebuddy/test/SimplePlugin.java (byte code enhancer):
package net.bytebuddy.test;
import net.bytebuddy.build.Plugin;
import net.bytebuddy.description.modifier.Visibility;
import net.bytebuddy.description.type.TypeDescription;
import net.bytebuddy.dynamic.DynamicType;
import net.bytebuddy.implementation.FieldAccessor;
public class SimplePlugin implements Plugin {
@Override
public boolean matches(TypeDescription target) {
return target.getName().equals("foo.Bar");
}
@Override
public DynamicType.Builder<?> apply(DynamicType.Builder<?> builder, TypeDescription typeDescription) {
if (typeDescription.getTypeName().equals("foo.Bar")) {
builder = builder.defineField("qux", String.class, Visibility.PRIVATE)
.defineMethod("getQux", String.class, Visibility.PUBLIC)
.intercept(FieldAccessor.ofField("qux"))
.defineMethod("setQux", void.class, Visibility.PUBLIC)
.withParameter(String.class)
.intercept(FieldAccessor.ofField("qux"));
}
return builder;
}
}
foo/Baz.java(引用动态类型的静态源文件):
package foo;
public class Baz {
private Bar bar = new Bar();
public String getQuux() {
return bar.getQux();
}
public void setQuux(String quux) {
bar.setQux(quux);
}
}
更新:Maven 似乎理解一个结构,该结构涉及一个具有增强字节代码和静态类源代码的合并模块,以及每个模块的单独模块,但是 IDE,IntelliJ 和 Eclipse 无法像 Maven 那样理解任何一种结构的类路径。