On Thu, Aug 20, 2020 at 7:57 AM Peter Lee wrote:
> Hi all,
>
> The builds in jenkins and github actions are failing.
> For jenkins, the java7, 14 and 16 builds are failing. As we have moved
> from JAVA 7 to 8, maybe we should disable java 7 build in jenkins? Besides
> the java 14 and 16 are also
On 17.08.20 08:29, Thomas Vandahl wrote:
> This has been a major overhaul of JCS with many adjustments for JDK 8+,
> better concurrency and logging. Finally, I would like to
> release Apache Commons JCS 3.0.
More than 72 hours have now passed, and there have been the following
votes (in order of a
A key part of using other sources short of a clean room implementation is
if the license from these sources is compatible with our Apache license.
Gary
On Fri, Aug 21, 2020, 03:45 Xeno Amess wrote:
> Yes, Pac200 is already removed from jdk lib...
> So what is the solution?
> We have to face thi
@Peter Lee
Sorry if I miss anything.
>We have already discussed this before.
I remember in an old thread we discussed about this, but I have no idea
whether we've already made a decision.
I see Emmanuel Bourg trying to maintain a p200 fork, so will we use it?
I just didn't get what the final decis
Hi Xeno,
This is another topic. We have already discussed this before. You can check the
old thread.
I'm only talking about the build failures here.
cheers,
Lee
On 8 21 2020, at 4:04 , Xeno Amess wrote:
> though each of the ways have some quite annoying things.
> 1. we remove Pac200 as well, as
though each of the ways have some quite annoying things.
1. we remove Pac200 as well, as jdk do.
will break BC.
2. we fork the Pac200 from jdk and create a new lib for it, and we invoke
that lib instead of jdk's Pac200.
if we change the package name, see 3.
if we do not change the package name, it
Yes, Pac200 is already removed from jdk lib...
So what is the solution?
We have to face this someday eventually, so why not today?
I can only get ideas of 2 ways...
1. we remove Pac200 as well, as jdk do.
2. we fork the Pac200 from jdk and create a new lib for it, and we invoke
that lib instead o
> Compress master now requires Java 8, so we can drop Java 7 from Jenkins,
> please do go ahead.
>
Done.
> For Java 14 and up, failures are due to the removal of Pack200 support from
> the JDK.
>
Yes, we all know this. Before we managed to figure out the solution, I'm just
thinking if we shoul
