Hi Dave, > I'm using exec-maven-plugin to call a main in my code that uses > javassist to generate a class file at build time.
The more common pattern is to generate .java source files, and then include them in the build. Since you are generating .class file(s), could you do it in a separate module of a multi-module build, then add that module as a dependency to your main project module? Could you post an MCVE, particularly your POM, which shows your current approach? Regards, Curtis -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden On Thu, Apr 6, 2017 at 10:48 AM, David Hoffer <dhoff...@gmail.com> wrote: > I'm using exec-maven-plugin to call a main in my code that uses javassist > to generate a class file at build time. My code places the class file in > the ./target/classes folder so it gets included in the modules normal > binary jar. > > However the rest of the build and other code needs to know that the class > exists. I've added that module/artifact as a dependency but the build and > the runtime classpath has no idea that class exists. > > How do I add it to the build and runtime classpath? > > -Dave >
