I think `maven-enforcer-plugin` config comes from jclouds/jclouds, do we want
to override only for `jclouds/jclouds-jaraf` ?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/108#
According to
[this](http://karaf.922171.n3.nabble.com/compilation-failing-with-karaf-4-2-0-M2-td4052701.html)
it looks like that Maven >= 3.3.x is needed for the `karaf-maven-plugin` which
we use to validate the features can be installed.
I'd suggest configuring the `maven-enforcer-plugin` in th
rebuild please
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/108#issuecomment-391017105
@nacx I'd appreciate your test as the ASF builder is reporting a weird problem
I cannot reproduce locally, thanks!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/108#issuecomme
rebuild please
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-karaf/pull/108#issuecomment-390401266
- bump guava version to 21
- bump karaf version to 4.2.0 to support java 8/9/10
- fix karaf-maven-plugin to use javase 1.8
this is required for https://github.com/jclouds/jclouds-labs/pull/436
You can view, comment on, or merge this pull request online at:
https://github.com/jclouds/jclouds-kar
