Hi,
Ok … turns out it was a combination of things I had to do.
In the end this configuration worked:
org.apache.maven.plugins
maven-surefire-plugin
2.20
**/*Test.class
${project.build.testOutputDirectory}
Hi Karl Heinz,
I’m already working on this. Now I’m simply setting up a set of “pure-pom”
modules. I got the dependency plugin to unpack the jar to “target/classes” and
test-jar to “target/test-classes” and retrolambda is correctly transforming
them there. Even the animalsniffer is now happy
Hi,
On 17/06/17 16:23, Christofer Dutz wrote:
I Karl Heinz,
I think that’s a really good idea … unfortunately I can’t seem to be able to
run the retrolambda plugin on jars, so I might setup little projects, that use
the dependency-plugin to unpack the jars and test-jars first and run the
I Karl Heinz,
I think that’s a really good idea … unfortunately I can’t seem to be able to
run the retrolambda plugin on jars, so I might setup little projects, that use
the dependency-plugin to unpack the jars and test-jars first and run the
retrolambda on them and then package them back.
Hi,
I would make a separate module for java8 and run there the retrolambda-
maven-plugin and another separate module for java7 and run there the
retrolambda-
maven-plugin as well...than you can make a separate jar file for each ...
No need for different executions of the compiler plugins etc.
Instead of tweaking the version, I would configure an executions of the
compiler plugins compile and testcompile goals to a separate output folders,
like ${build.directory}${file.separator}classes-java7 and
${build.directory}${file.separator}test-classes-java7 and then an execution of
the jar
