Re: Updating for future jdk versions

That's terrific! Thanks for looking into this.  I have been so busy I 
forgot :-) We should be thinking about our roadmap - moving beyond Java8 
and maybe Java servlet 4.0 (2017 release) or 4.1?

-
Jeffery


On 7/30/19 11:23 AM, Georg Kallidis wrote:
> Hi Jeffery,
>
> it's important to be aware of all this, java 11+x - we might use jenkins
> CI to check for any issues and cleanup or define Fulcrums as dormant at
> least ..
>
> Currently JSON is already updated with a java12 profile. Commons-Email
> seems to be of some value as a lightweighted debugging tool, I removed
> CORBA inputstream - this code was not tested anyway - with normal
> java.io.inputstream (the original intent may be of eqal appropriateness if
> using this class), using now Junit5 and log4j2. But some components are
> for the attic, I agree.
>
> Fulcrum-Jetty I have not yet investigated, though..
>
> Best regards, Georg
>
>
>
>
> Von:    Jeffery Painter <[email protected]>
> An:     [email protected]
> Datum:  23.07.2019 19:44
> Betreff:        Updating for future jdk versions
>
>
>
> Hi turbine devs,
>
>
> I just went through and tested building fulcrum components with
> jdk-12.0.2 (latest) and pushed a couple of updates that allowed for some
> of the broken components to build.  Georg - json has some issues still
> that I did not work out that will need to be addressed.  Also
> commonsemail (move to attic?) makes a single call to a CORBA InputStream
> that would require either replacing or adding the required modules to
> the build profile.  However, I think this is one of several components
> we can probably move to the attic.
>
> fulcrum-jetty was giving me some issues building just as is (test seemed
> to hang) but not sure if that is just my machine or something else.
>
> I'm not sure what our roadmap looks like to move beyond Java8, but we
> should start thinking about it.  Hopefully this exercise is of help in
> that effort :-)
>
>
> -
>
> Jeffery
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>