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 <pottlin...@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" <pottlin...@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]
