You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@edgent.apache.org by Julian Feinauer <j....@pragmaticminds.de> on 2019/03/31 18:15:18 UTC
Did I kill the develop?
Hi all,
I just merged my api refactoring and it seems that Jenkins doesn’t like it.
I checked it multiple times and the build compiles locally on my machine (well, the HTTP tests seem to require some Inet access which I don’t have, but the ETIAO Runtime module builds fine).
Can someone else check that?
Or am I missing something?
Thanks
Julian
Re: Did I kill the develop?
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi Chris,
thanks for this information... I will have a look and try to fix it.
Julian
Am 01.04.19, 08:51 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi all,
Please also read the content of the DEVELOPMENT.md as this contains all of this information.
Chris
Am 01.04.19, 08:50 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi Julian,
from a quick look it seems that you only addressed the artifacts in the main platform (java8) ... in the platforms section we have matching maven modules for every main module.
The difference is that the java8 versions built first are unpacked into the target/classes directory and there the retrolambda plugin translates lambda code into java7 code hereby
Making the code compatible with java7. Also the test-classes are unpacked too and the tests are then executed with a java7 VM.
As you didn't adjust these artifacts of course they are trying to fetch things it can't get anymore. So there modules need adjusting too.
Also in the distribution module a big archive with binary artifacts is built ... this order list must reference only existing modules.
In order to execute all of these, please activate the following maven profiles:
- distribution
- platform-java7
- platform-android
Chris
Am 01.04.19, 08:43 schrieb "Julian Feinauer" <j....@pragmaticminds.de>:
Hi,
thanks to both of you!
What I see in the logs is something with the Retrolambda Plugin and I have absolutely no experience with that... so I would be super grateful if you (chris) could look into this.
Julian
Am 01.04.19, 08:20 schrieb "Christofer Dutz" <ch...@c-ware.de>:
I'll look into this ASAP
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Gayashan Amarasinghe <ga...@gmail.com>
Sent: Monday, April 1, 2019 3:10:46 AM
To: dev@edgent.apache.org
Subject: Re: Did I kill the develop?
HI Julian,
I did a fresh clone and clean build without tests and it compiled
successfully. When I ran with tests they failed at websockets, probably an
intermittent issue. Sorry didn't have enough time to dig in further. But
ETIAO runtime was built successfully. So I don't think the api refactoring
broke the build.
Best,
Gayashan
On Mon, Apr 1, 2019 at 5:15 AM Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi all,
>
> I just merged my api refactoring and it seems that Jenkins doesn’t like it.
> I checked it multiple times and the build compiles locally on my machine
> (well, the HTTP tests seem to require some Inet access which I don’t have,
> but the ETIAO Runtime module builds fine).
>
> Can someone else check that?
> Or am I missing something?
>
> Thanks
> Julian
>
Re: Did I kill the develop?
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi all,
Please also read the content of the DEVELOPMENT.md as this contains all of this information.
Chris
Am 01.04.19, 08:50 schrieb "Christofer Dutz" <ch...@c-ware.de>:
Hi Julian,
from a quick look it seems that you only addressed the artifacts in the main platform (java8) ... in the platforms section we have matching maven modules for every main module.
The difference is that the java8 versions built first are unpacked into the target/classes directory and there the retrolambda plugin translates lambda code into java7 code hereby
Making the code compatible with java7. Also the test-classes are unpacked too and the tests are then executed with a java7 VM.
As you didn't adjust these artifacts of course they are trying to fetch things it can't get anymore. So there modules need adjusting too.
Also in the distribution module a big archive with binary artifacts is built ... this order list must reference only existing modules.
In order to execute all of these, please activate the following maven profiles:
- distribution
- platform-java7
- platform-android
Chris
Am 01.04.19, 08:43 schrieb "Julian Feinauer" <j....@pragmaticminds.de>:
Hi,
thanks to both of you!
What I see in the logs is something with the Retrolambda Plugin and I have absolutely no experience with that... so I would be super grateful if you (chris) could look into this.
Julian
Am 01.04.19, 08:20 schrieb "Christofer Dutz" <ch...@c-ware.de>:
I'll look into this ASAP
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Gayashan Amarasinghe <ga...@gmail.com>
Sent: Monday, April 1, 2019 3:10:46 AM
To: dev@edgent.apache.org
Subject: Re: Did I kill the develop?
HI Julian,
I did a fresh clone and clean build without tests and it compiled
successfully. When I ran with tests they failed at websockets, probably an
intermittent issue. Sorry didn't have enough time to dig in further. But
ETIAO runtime was built successfully. So I don't think the api refactoring
broke the build.
Best,
Gayashan
On Mon, Apr 1, 2019 at 5:15 AM Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi all,
>
> I just merged my api refactoring and it seems that Jenkins doesn’t like it.
> I checked it multiple times and the build compiles locally on my machine
> (well, the HTTP tests seem to require some Inet access which I don’t have,
> but the ETIAO Runtime module builds fine).
>
> Can someone else check that?
> Or am I missing something?
>
> Thanks
> Julian
>
Re: Did I kill the develop?
Posted by Christofer Dutz <ch...@c-ware.de>.
Hi Julian,
from a quick look it seems that you only addressed the artifacts in the main platform (java8) ... in the platforms section we have matching maven modules for every main module.
The difference is that the java8 versions built first are unpacked into the target/classes directory and there the retrolambda plugin translates lambda code into java7 code hereby
Making the code compatible with java7. Also the test-classes are unpacked too and the tests are then executed with a java7 VM.
As you didn't adjust these artifacts of course they are trying to fetch things it can't get anymore. So there modules need adjusting too.
Also in the distribution module a big archive with binary artifacts is built ... this order list must reference only existing modules.
In order to execute all of these, please activate the following maven profiles:
- distribution
- platform-java7
- platform-android
Chris
Am 01.04.19, 08:43 schrieb "Julian Feinauer" <j....@pragmaticminds.de>:
Hi,
thanks to both of you!
What I see in the logs is something with the Retrolambda Plugin and I have absolutely no experience with that... so I would be super grateful if you (chris) could look into this.
Julian
Am 01.04.19, 08:20 schrieb "Christofer Dutz" <ch...@c-ware.de>:
I'll look into this ASAP
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Gayashan Amarasinghe <ga...@gmail.com>
Sent: Monday, April 1, 2019 3:10:46 AM
To: dev@edgent.apache.org
Subject: Re: Did I kill the develop?
HI Julian,
I did a fresh clone and clean build without tests and it compiled
successfully. When I ran with tests they failed at websockets, probably an
intermittent issue. Sorry didn't have enough time to dig in further. But
ETIAO runtime was built successfully. So I don't think the api refactoring
broke the build.
Best,
Gayashan
On Mon, Apr 1, 2019 at 5:15 AM Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi all,
>
> I just merged my api refactoring and it seems that Jenkins doesn’t like it.
> I checked it multiple times and the build compiles locally on my machine
> (well, the HTTP tests seem to require some Inet access which I don’t have,
> but the ETIAO Runtime module builds fine).
>
> Can someone else check that?
> Or am I missing something?
>
> Thanks
> Julian
>
Re: Did I kill the develop?
Posted by Julian Feinauer <j....@pragmaticminds.de>.
Hi,
thanks to both of you!
What I see in the logs is something with the Retrolambda Plugin and I have absolutely no experience with that... so I would be super grateful if you (chris) could look into this.
Julian
Am 01.04.19, 08:20 schrieb "Christofer Dutz" <ch...@c-ware.de>:
I'll look into this ASAP
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Gayashan Amarasinghe <ga...@gmail.com>
Sent: Monday, April 1, 2019 3:10:46 AM
To: dev@edgent.apache.org
Subject: Re: Did I kill the develop?
HI Julian,
I did a fresh clone and clean build without tests and it compiled
successfully. When I ran with tests they failed at websockets, probably an
intermittent issue. Sorry didn't have enough time to dig in further. But
ETIAO runtime was built successfully. So I don't think the api refactoring
broke the build.
Best,
Gayashan
On Mon, Apr 1, 2019 at 5:15 AM Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi all,
>
> I just merged my api refactoring and it seems that Jenkins doesn’t like it.
> I checked it multiple times and the build compiles locally on my machine
> (well, the HTTP tests seem to require some Inet access which I don’t have,
> but the ETIAO Runtime module builds fine).
>
> Can someone else check that?
> Or am I missing something?
>
> Thanks
> Julian
>
Re: Did I kill the develop?
Posted by Christofer Dutz <ch...@c-ware.de>.
I'll look into this ASAP
Outlook für Android<https://aka.ms/ghei36> herunterladen
________________________________
From: Gayashan Amarasinghe <ga...@gmail.com>
Sent: Monday, April 1, 2019 3:10:46 AM
To: dev@edgent.apache.org
Subject: Re: Did I kill the develop?
HI Julian,
I did a fresh clone and clean build without tests and it compiled
successfully. When I ran with tests they failed at websockets, probably an
intermittent issue. Sorry didn't have enough time to dig in further. But
ETIAO runtime was built successfully. So I don't think the api refactoring
broke the build.
Best,
Gayashan
On Mon, Apr 1, 2019 at 5:15 AM Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi all,
>
> I just merged my api refactoring and it seems that Jenkins doesn’t like it.
> I checked it multiple times and the build compiles locally on my machine
> (well, the HTTP tests seem to require some Inet access which I don’t have,
> but the ETIAO Runtime module builds fine).
>
> Can someone else check that?
> Or am I missing something?
>
> Thanks
> Julian
>
Re: Did I kill the develop?
Posted by Gayashan Amarasinghe <ga...@gmail.com>.
HI Julian,
I did a fresh clone and clean build without tests and it compiled
successfully. When I ran with tests they failed at websockets, probably an
intermittent issue. Sorry didn't have enough time to dig in further. But
ETIAO runtime was built successfully. So I don't think the api refactoring
broke the build.
Best,
Gayashan
On Mon, Apr 1, 2019 at 5:15 AM Julian Feinauer <j....@pragmaticminds.de>
wrote:
> Hi all,
>
> I just merged my api refactoring and it seems that Jenkins doesn’t like it.
> I checked it multiple times and the build compiles locally on my machine
> (well, the HTTP tests seem to require some Inet access which I don’t have,
> but the ETIAO Runtime module builds fine).
>
> Can someone else check that?
> Or am I missing something?
>
> Thanks
> Julian
>