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 <[email protected]> Sent: Saturday, January 20, 2018 4:38:42 PM To: [email protected] 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
