You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "P. Ottlinger" <po...@apache.org> on 2018/01/02 08:59:12 UTC
configjsr branch not buildable in travis / other Travis builds are ok
except CDI test failures in extensions
Hi everyone,
happy new year.
@Anatole: can you try to convince the configJSR guys to make at least a
SNAPSHOT of their API available via Maven?
My comment on github is still ignored ... maybe you achieve more via
direct contact.
As long as we do not have a publicly available API artefact Travis still
fails:
https://travis-ci.org/apache/incubator-tamaya
Master is still okay:
https://travis-ci.org/apache/incubator-tamaya/branches
Sandbox seems to be okay:
https://travis-ci.org/apache/incubator-tamaya-sandbox/branches
while extension is not building on Travis (just like ASF-Jenkins):
https://travis-ci.org/apache/incubator-tamaya-extensions/branches
The same CDI-test failures:
https://api.travis-ci.org/v3/job/323041944/log.txt
Cheers,
Phil
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by "P. Ottlinger" <po...@apache.org>.
Am 25.01.2018 um 08:45 schrieb William Lieurance:
> Sure thing. The request is at https://github.com/apache/incubator-tamaya/pull/9
>
> Let me know if you'd like a patch file on the Jira ticket instead.
All went fine - I do hope that Travis will turn green again
(at the moment the build is waiting in the queue).
Thanks for your help and the introduction of jitpack.
Phil
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by William Lieurance <wi...@namikoda.com>.
Sure thing. The request is at https://github.com/apache/incubator-tamaya/pull/9
Let me know if you'd like a patch file on the Jira ticket instead.
--William
________________________________________
From: P. Ottlinger <po...@apache.org>
Sent: Wednesday, January 24, 2018 3:45:51 PM
To: dev@tamaya.incubator.apache.org
Subject: Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions
Hi *,
Am 21.01.2018 um 04:55 schrieb William Lieurance:
> While I would definitely like to see javaconfig-api jars published correctly, as long as we're talking about bad workarounds I was able to get Anatole's branch built and tests passing using jitpack.io as a passthrough to their github repo. I'm not proud of it but I think it can get us moving until the jsr folks can get around to publishing. See https://github.com/peculater/incubator-tamaya/compare/configjsr...configjsr-jitpack?expand=1
created
https://issues.apache.org/jira/browse/TAMAYA-325
for that.
@William: please proceed with a merge request - it should be possible to
do this via Github.
Please give it a try,
thanks
Phil
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by "P. Ottlinger" <po...@apache.org>.
Hi *,
Am 21.01.2018 um 04:55 schrieb William Lieurance:
> While I would definitely like to see javaconfig-api jars published correctly, as long as we're talking about bad workarounds I was able to get Anatole's branch built and tests passing using jitpack.io as a passthrough to their github repo. I'm not proud of it but I think it can get us moving until the jsr folks can get around to publishing. See https://github.com/peculater/incubator-tamaya/compare/configjsr...configjsr-jitpack?expand=1
created
https://issues.apache.org/jira/browse/TAMAYA-325
for that.
@William: please proceed with a merge request - it should be possible to
do this via Github.
Please give it a try,
thanks
Phil
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by Anatole Tresch <at...@gmail.com>.
+1
2018-01-22 21:35 GMT+01:00 P. Ottlinger <po...@apache.org>:
> William,
>
> thanks for the idea - I haven't heard of jitpack before.
>
> While Anatole tries to bring up the issue this would ease the build and
> provide a fixed / git hash version ....
>
> +1 for that.
>
> Any other opinions?
> Phil
>
> Am 21.01.2018 um 04:55 schrieb William Lieurance:
> > While I would definitely like to see javaconfig-api jars published
> correctly, as long as we're talking about bad workarounds I was able to get
> Anatole's branch built and tests passing using jitpack.io as a
> passthrough to their github repo. I'm not proud of it but I think it can
> get us moving until the jsr folks can get around to publishing. See
> https://github.com/peculater/incubator-tamaya/compare/
> configjsr...configjsr-jitpack?expand=1
> >
> > --William
>
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
*Speaking at:*
[image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by "P. Ottlinger" <po...@apache.org>.
William,
thanks for the idea - I haven't heard of jitpack before.
While Anatole tries to bring up the issue this would ease the build and
provide a fixed / git hash version ....
+1 for that.
Any other opinions?
Phil
Am 21.01.2018 um 04:55 schrieb William Lieurance:
> While I would definitely like to see javaconfig-api jars published correctly, as long as we're talking about bad workarounds I was able to get Anatole's branch built and tests passing using jitpack.io as a passthrough to their github repo. I'm not proud of it but I think it can get us moving until the jsr folks can get around to publishing. See https://github.com/peculater/incubator-tamaya/compare/configjsr...configjsr-jitpack?expand=1
>
> --William
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by William Lieurance <wi...@namikoda.com>.
While I would definitely like to see javaconfig-api jars published correctly, as long as we're talking about bad workarounds I was able to get Anatole's branch built and tests passing using jitpack.io as a passthrough to their github repo. I'm not proud of it but I think it can get us moving until the jsr folks can get around to publishing. See https://github.com/peculater/incubator-tamaya/compare/configjsr...configjsr-jitpack?expand=1
--William
________________________________________
From: P. Ottlinger <po...@apache.org>
Sent: Saturday, January 20, 2018 4:38:42 PM
To: dev@tamaya.incubator.apache.org
Subject: Re: configjsr branch not buildable in travis / other Travis builds are ok except CDI test failures in extensions
Am 20.01.2018 um 23:21 schrieb Anatole Tresch:
> Maybe, we can build it locally and checkin the jars temporarely into our
> sources and add them with system dependency into Maven? WDYT?
I fear we'll never get rid of this workaround ....
are there any reasons no JARs are published yet?!
Or is it the same like our 0.3 release - we just did not find time to
publish it properly ....
Cheers,
Phil
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by Anatole Tresch <at...@gmail.com>.
I assume it is because there is still discussions ongoing related the API.
I will definitvely ask for this or even raise a ticket. I assume with Early
Draft Review the latest, we will have an artifact accessible ;-)
J Anatole
2018-01-20 23:38 GMT+01:00 P. Ottlinger <po...@apache.org>:
> Am 20.01.2018 um 23:21 schrieb Anatole Tresch:
> > Maybe, we can build it locally and checkin the jars temporarely into our
> > sources and add them with system dependency into Maven? WDYT?
>
> I fear we'll never get rid of this workaround ....
> are there any reasons no JARs are published yet?!
>
> Or is it the same like our 0.3 release - we just did not find time to
> publish it properly ....
>
> Cheers,
> Phil
>
>
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
*Speaking at:*
[image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by "P. Ottlinger" <po...@apache.org>.
Am 20.01.2018 um 23:21 schrieb Anatole Tresch:
> Maybe, we can build it locally and checkin the jars temporarely into our
> sources and add them with system dependency into Maven? WDYT?
I fear we'll never get rid of this workaround ....
are there any reasons no JARs are published yet?!
Or is it the same like our 0.3 release - we just did not find time to
publish it properly ....
Cheers,
Phil
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by Anatole Tresch <at...@gmail.com>.
Maybe, we can build it locally and checkin the jars temporarely into our
sources and add them with system dependency into Maven? WDYT?
2018-01-20 23:19 GMT+01:00 Anatole Tresch <at...@gmail.com>:
> No, sorry. I was completely under water this week with customer work, I
> even missed the JSR meeting on Thursday ;-(
>
> J Anatole
>
> 2018-01-20 22:20 GMT+01:00 P. Ottlinger <po...@apache.org>:
>
>> @Anatole:
>> any news concerning an official JSR API deployment?
>>
>> https://travis-ci.org/apache/incubator-tamaya/branches
>>
>> configjsr still not buildable.
>>
>> Thanks,
>> Phil
>>
>> Am 02.01.2018 um 13:15 schrieb Anatole Tresch:
>> > Hi Phil
>> > I will take that up with them.
>> > Currently I am working on the extensions, they definitely do not build
>> now.
>> > Good news is I have all CDI stuff building so I assume I will be faster
>> > with the outstanding modules...
>> >
>> > J and Happy New Year!
>> > Anatole
>> >
>> > Am 02.01.2018 09:59 schrieb "P. Ottlinger" <po...@apache.org>:
>> >
>> >> Hi everyone,
>> >>
>> >> happy new year.
>> >>
>> >> @Anatole: can you try to convince the configJSR guys to make at least a
>> >> SNAPSHOT of their API available via Maven?
>> >>
>> >> My comment on github is still ignored ... maybe you achieve more via
>> >> direct contact.
>> >>
>> >> As long as we do not have a publicly available API artefact Travis
>> still
>> >> fails:
>> >> https://travis-ci.org/apache/incubator-tamaya
>> >>
>> >> Master is still okay:
>> >> https://travis-ci.org/apache/incubator-tamaya/branches
>> >>
>> >>
>> >> Sandbox seems to be okay:
>> >> https://travis-ci.org/apache/incubator-tamaya-sandbox/branches
>> >> while extension is not building on Travis (just like ASF-Jenkins):
>> >> https://travis-ci.org/apache/incubator-tamaya-extensions/branches
>> >>
>> >> The same CDI-test failures:
>> >> https://api.travis-ci.org/v3/job/323041944/log.txt
>> >>
>> >> Cheers,
>> >> Phil
>> >>
>> >
>>
>>
>
>
> --
> *Anatole Tresch*
> PPMC Member Apache Tamaya
> JCP Star Spec Lead
> *Switzerland, Europe Zurich, GMT+1*
> *maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
> *Twitter: @atsticks, @tamayaconf*
>
> *Speaking at:*
>
> [image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
>
>
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
*Speaking at:*
[image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by Anatole Tresch <at...@gmail.com>.
No, sorry. I was completely under water this week with customer work, I
even missed the JSR meeting on Thursday ;-(
J Anatole
2018-01-20 22:20 GMT+01:00 P. Ottlinger <po...@apache.org>:
> @Anatole:
> any news concerning an official JSR API deployment?
>
> https://travis-ci.org/apache/incubator-tamaya/branches
>
> configjsr still not buildable.
>
> Thanks,
> Phil
>
> Am 02.01.2018 um 13:15 schrieb Anatole Tresch:
> > Hi Phil
> > I will take that up with them.
> > Currently I am working on the extensions, they definitely do not build
> now.
> > Good news is I have all CDI stuff building so I assume I will be faster
> > with the outstanding modules...
> >
> > J and Happy New Year!
> > Anatole
> >
> > Am 02.01.2018 09:59 schrieb "P. Ottlinger" <po...@apache.org>:
> >
> >> Hi everyone,
> >>
> >> happy new year.
> >>
> >> @Anatole: can you try to convince the configJSR guys to make at least a
> >> SNAPSHOT of their API available via Maven?
> >>
> >> My comment on github is still ignored ... maybe you achieve more via
> >> direct contact.
> >>
> >> As long as we do not have a publicly available API artefact Travis still
> >> fails:
> >> https://travis-ci.org/apache/incubator-tamaya
> >>
> >> Master is still okay:
> >> https://travis-ci.org/apache/incubator-tamaya/branches
> >>
> >>
> >> Sandbox seems to be okay:
> >> https://travis-ci.org/apache/incubator-tamaya-sandbox/branches
> >> while extension is not building on Travis (just like ASF-Jenkins):
> >> https://travis-ci.org/apache/incubator-tamaya-extensions/branches
> >>
> >> The same CDI-test failures:
> >> https://api.travis-ci.org/v3/job/323041944/log.txt
> >>
> >> Cheers,
> >> Phil
> >>
> >
>
>
--
*Anatole Tresch*
PPMC Member Apache Tamaya
JCP Star Spec Lead
*Switzerland, Europe Zurich, GMT+1*
*maketechsimple.wordpress.com <http://maketechsimple.wordpress.com/> *
*Twitter: @atsticks, @tamayaconf*
*Speaking at:*
[image: JSD_Speaker_2017][image: J-Con 2017 logo][image: JVM Con]
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by "P. Ottlinger" <po...@apache.org>.
@Anatole:
any news concerning an official JSR API deployment?
https://travis-ci.org/apache/incubator-tamaya/branches
configjsr still not buildable.
Thanks,
Phil
Am 02.01.2018 um 13:15 schrieb Anatole Tresch:
> Hi Phil
> I will take that up with them.
> Currently I am working on the extensions, they definitely do not build now.
> Good news is I have all CDI stuff building so I assume I will be faster
> with the outstanding modules...
>
> J and Happy New Year!
> Anatole
>
> Am 02.01.2018 09:59 schrieb "P. Ottlinger" <po...@apache.org>:
>
>> Hi everyone,
>>
>> happy new year.
>>
>> @Anatole: can you try to convince the configJSR guys to make at least a
>> SNAPSHOT of their API available via Maven?
>>
>> My comment on github is still ignored ... maybe you achieve more via
>> direct contact.
>>
>> As long as we do not have a publicly available API artefact Travis still
>> fails:
>> https://travis-ci.org/apache/incubator-tamaya
>>
>> Master is still okay:
>> https://travis-ci.org/apache/incubator-tamaya/branches
>>
>>
>> Sandbox seems to be okay:
>> https://travis-ci.org/apache/incubator-tamaya-sandbox/branches
>> while extension is not building on Travis (just like ASF-Jenkins):
>> https://travis-ci.org/apache/incubator-tamaya-extensions/branches
>>
>> The same CDI-test failures:
>> https://api.travis-ci.org/v3/job/323041944/log.txt
>>
>> Cheers,
>> Phil
>>
>
Re: configjsr branch not buildable in travis / other Travis builds
are ok except CDI test failures in extensions
Posted by Anatole Tresch <at...@gmail.com>.
Hi Phil
I will take that up with them.
Currently I am working on the extensions, they definitely do not build now.
Good news is I have all CDI stuff building so I assume I will be faster
with the outstanding modules...
J and Happy New Year!
Anatole
Am 02.01.2018 09:59 schrieb "P. Ottlinger" <po...@apache.org>:
> Hi everyone,
>
> happy new year.
>
> @Anatole: can you try to convince the configJSR guys to make at least a
> SNAPSHOT of their API available via Maven?
>
> My comment on github is still ignored ... maybe you achieve more via
> direct contact.
>
> As long as we do not have a publicly available API artefact Travis still
> fails:
> https://travis-ci.org/apache/incubator-tamaya
>
> Master is still okay:
> https://travis-ci.org/apache/incubator-tamaya/branches
>
>
> Sandbox seems to be okay:
> https://travis-ci.org/apache/incubator-tamaya-sandbox/branches
> while extension is not building on Travis (just like ASF-Jenkins):
> https://travis-ci.org/apache/incubator-tamaya-extensions/branches
>
> The same CDI-test failures:
> https://api.travis-ci.org/v3/job/323041944/log.txt
>
> Cheers,
> Phil
>