I forgot to mention something here, which makes it a bit more of a nuanced 
decision.  The default repos from Ubuntu are set up such that:

        OpenJDK 7 = 14.04 (Trusty)
        OpenJDK 8 = 16.04 (Xenial)

        All of the “get 7 on 16.04” and “get 8 on 14.04” I’ve seen have not 
been… appealing.  (“Figure out which deb you need, then…”  or “add the trusty 
repos temporarily” or … yeah.  Not good.)


        So if we want to stick with 7, then that means sticking with Trusty.

> On May 31, 2017, at 1:06 PM, Sean Busbey <[email protected]> wrote:
> 
> I'd love a 0.5.0 release, FWIW.
> 
> Would pulling down openjdk 7 artifacts go more reliably? That would
> presumably be a bit less disruptive than also jumping to jdk8.
> 
> (for clarity, I don't think this is too aggressive, since the default
> is just an exemplar and folks could always roll their own.)
> 
> On Wed, May 31, 2017 at 1:39 PM, Allen Wittenauer
> <[email protected]> wrote:
>> 
>>        It looks like our default Docker image that we ship with Yetus is 
>> failing to build because it can’t download stuff from Oracle.  Given that we 
>> probably should do at least something to fix it :), I thought it might be 
>> time to actually just upgrade the image completely.  I’ve filed YETUS-512 
>> which does the following:
>> 
>>        * Switches the base OS to Ubuntu Xenial 16.04
>>        * Removes all of the Oracle JDK bits
>>        * Switches the JDK to OpenJDK 8 (Headless)
>>        * Removes a bunch of hacks that are no longer necessary
>> 
>>        As a result, this one builds significantly faster and is a tad bit 
>> smaller. If we think that’s too aggressive, then the alternative is to just 
>> remove the Oracle JDK7 bits from the current image.  Either way, we’re 
>> looking at an incompatible/disruptive change.
>> 
>>        Sidenote: I’m currently trying to go through all of the 0.5.0 open 
>> issues.  My goal is to work towards a release relatively soon, but no 
>> promises.  Haven’t decided yet whether I’m going to tackle some of the 
>> bigger issues yet.
>> 
>> Thanks.

Reply via email to