Re: java: switch to icedtea-8 as default JDK

[Gábor Boskovits]

2018-01-06 21:16 GMT+01:00 Gábor Boskovits <address@hidden>:

Actually we still have a couple of build failures, some test failures, and the

commit messages are not conformant to the policy. Currently making the few remainig

failures work should be the primary task. I will check the details.

I already have an integration branch where I reorder commits and make commit messages conform.

It would also be nice, if you could review the patches already sent to guix-patches.

They are tagged [PATCH core-updates]. I guess we are waiting for the next core-updates cycle, until then

these will not be pushed.

These are the backwards compatible changes collected so far.

Soon I will add the fix for the antlr3 bootstrap toolchain.

Current issues:

https://github.com/Boskovits/guix/issues/61

I'm will contact upstream to check if this issue is serious.

Will cc to you.

https://github.com/Boskovits/guix/issues/58

I will have a look at this once more.

I've already solved two similar issues, I guess I can cope with this.

I could not find an good solution to this one. I could make it only with

setting jdk and ant back to java7, and disabling tests.

I've tried several things, but it seems that a java7

bootstrap classpatch is required anyways.

I would recommend for now setting this as java7 build, and remove this

package when beanutils goes to 2.0.0. They've just started this iteration

according to jira, and the first things will be upgrading to collections4.

If you have any idea on how to solve this, please comment.

There are several distro patches, we might adapt one of them, but

this can't be solved in a backwards compatible way.

What I don't understand, is why setting source and target to 1.7,

like I did on java-aqute-libg did not work.

 

https://github.com/Boskovits/guix/issues/57

I'm not sure about this one.

I can try to check upstream if this is a problem on their site, but it seems not.

It seems that some zeromq calls fail.

Can this be related to our build container?

 

Fixed this by updating. it turned out to be an upstream bug. 

https://github.com/Boskovits/guix/issues/56

I haven't looked into this one yet.

https://github.com/Boskovits/guix/issues/55

I intend to remove this package if

axoloti-patcher works with the current version.

I did not do this yet, because the

java-simple-xml issue also blocks axoloti-patcher,

so I could not check yet if the current version is ok.

The remaining five issues are the packages from

the covering of icedtea7 that do not build.

The rest does build.

java-plexus-default-container now builds.

 

I don't know if we have any more issues between the

marked problems and these five packages.

--
Chris