Github user chinmaykolhatkar commented on the issue:
https://github.com/apache/bigtop/pull/188
@c0s @rvs @tweise Made the changes. I had to add a diff for apex to compile
successfully with 2.7.x.
The reason for the patch is captured here for reference: APEXCORE-679
In futu
Github user chinmaykolhatkar commented on a diff in the pull request:
https://github.com/apache/bigtop/pull/188#discussion_r107836097
--- Diff: bigtop-packages/src/common/apex/do-component-build ---
@@ -28,6 +28,9 @@ command -v mvn > /dev/null 2>&1 || {
# Build apex
mvn cl
GitHub user kwmonroe opened a pull request:
https://github.com/apache/bigtop/pull/189
BIGTOP-2712: Juju CI driven updates
The original point of this branch was to refresh the hbase charm (readme
was out-of-date, needed lint love). However, as soon as ran CI on this and
recent chan
Here is the link for 1.8.0_111
https://launchpad.net/~openjdk-r/+archive/ubuntu/security/+build/11087717
Thanks,
Ganesh
On Thu, Mar 23, 2017 at 3:28 PM, Olaf Flebbe wrote:
> >>
> >> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
> >> see two ways:
> >> 1. Downgrade ope
Hi!
recent issues surrounding builds on two of
our two non-x86 platforms got me thinking
that while it is fun to build on them (to iron out
kinds in JDK and what not) we don't actually
have to release the packages for most of the
projects since all those are arch independent.
The only ones that AR
> Am 23.03.2017 um 21:33 schrieb Roman Shaposhnik :
>
> There's no 111 :-(
Yep, ubuntu seems to have replaced all 111 packages by 121. And yes, our
current docker image still has 111. My-o-my.
Guess going back is no option, at least not without compiling java ourself or
grabbing it from a dubi
There's no 111 :-(
Jun, Naresh, Ganesh, out of the list available on the URL Olaf
provided -- what should we pick?
Thanks,
Roman.
On Thu, Mar 23, 2017 at 1:28 PM, Olaf Flebbe wrote:
>>>
>>> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
>>> see two ways:
>>> 1. Downgra
>>
>> So for the incoming 1.2.0 release, to fix this on aarch64/ubuntu-16.04 I
>> see two ways:
>> 1. Downgrade open-jdk to 1.8.0_111. This needs to change bigtop_toolchain/
>> manifests/jdk.pp
>
> I'd vote for this option. But I've got to ask: where do I get that exact
> version
> for ubuntu 16
On Thu, Mar 23, 2017 at 7:36 AM, Ganesh Raju wrote:
> Forwarding to dev mailing list. Any thoughts ?
>
> Thanks
> Ganesh Raju
>
>
> -- Forwarded message --
> From: Jun He
> Date: Thu, Mar 23, 2017 at 5:10 AM
> Subject: Build failed due to OpenJDK 1.8.0_121 changes
> To: Roman Shap
Github user c0s commented on a diff in the pull request:
https://github.com/apache/bigtop/pull/188#discussion_r107769130
--- Diff: bigtop-packages/src/common/apex/do-component-build ---
@@ -28,6 +28,9 @@ command -v mvn > /dev/null 2>&1 || {
# Build apex
mvn clean package -
With any luck we are going to upgrade to Ignite 1.9 which has this issue fixed.
--
Take care,
Konstantin (Cos) Boudnik
2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622
Disclaimer: Opinions expressed in this email are those of the author,
and do not necessarily represent the views of any compan
Forwarding to dev mailing list. Any thoughts ?
Thanks
Ganesh Raju
-- Forwarded message --
From: Jun He
Date: Thu, Mar 23, 2017 at 5:10 AM
Subject: Build failed due to OpenJDK 1.8.0_121 changes
To: Roman Shaposhnik , Ganesh Raju
Cc: Naresh Bhat , Eugene Xie ,
Tone Zhang , Yuqi G
12 matches
Mail list logo
