Regarding java8 and java7 artifacts …
This could be problematic, if we wanted to publish both.
Having a binary tar.gz with a java8 and one with java7 doesn’t seem to be a
problem, but having two artifacts deployed to Maven-Central is no trivial task.
Exactly this type of jars for different java
> On Jun 8, 2017, at 4:19 AM, Christofer Dutz wrote:
>
> Regarding java8 and java7 artifacts …
Coincidentally, I started investigating this space yesterday and
retrolambda-maven-plugin
and was just composing mail on the question of publishing java8 and java7 to
mvn
Hi Dale,
Today I had some progress on the java7 side.
I successfully added the retrolambda-maven-plugin in a dedicated java7 profile
to the main pom. Now the plugin automatically kicks in and converts the classes
after compiling them. I also added the animal-sniffer-maven-plugin to
explicitly
> On Jun 8, 2017, at 10:43 AM, Christofer Dutz
> wrote:
>
> Eventually your approach with a sub-directory inside the target would be a
> valid option … would probably have to adjust the maven-clean-plugin too, but
> that should work in getting all results inside
sorry no idea about travis and memory
On Jun 8, 2017, at 10:40 AM, Christofer Dutz wrote:
> ...
> Today I had some progress on the java7 side.
...
> problem. The default methods in DirectTestSetup can’t seem to be backported
> if the interface and the implementing