|Subject:||Re: java: switch to icedtea-8 as default JDK|
|Date:||Wed, 3 Jan 2018 14:06:31 +0100|
2017-12-20 13:29 GMT+01:00 Gábor Boskovits <address@hidden>:2017-12-20 11:34 GMT+01:00 Gábor Boskovits <address@hidden>:2017-12-19 23:11 GMT+01:00 Ricardo Wurmus <address@hidden>:
Gábor Boskovits <address@hidden> writes:
> Now I have another blocking issue:
> Error message:
> BUILD FAILED
.drv-0/beanshell-2.0b6/build.xIs it not just enough to add junit to the inputs of java-bsh? ml:654:
> Problem: failed to create task or type junit
> Cause: the class org.apache.tools.ant.taskdefs.
> not found.
No, unfortunately it seems to affect all packages using junit.I guess it is because I use ant/java8, and maybe that is more fussy about this...It seems, that we should add the lib flag to the nat commend line, if we havejunit as input. However junit has quite a big dependency graph with the newhamcrest-core fix, but that is needed for junit. I think we should discuss our options here,I don't feel comfortable to make such a decision without prior discussion.Regarding this issue, in my opinion we cloud do the following:Add two parameters to ant build system:junit?junitIf junit? then force use of junit, if not, then force not to use it, if unspecified check if we have junit in build.inputs, and use it if it is.junit should default to java-junit, like we have for icedtea, and ant.Can something like this be done?It would be nice if the ant-build-system needed junit only if it is in build-inputs, or explicitly requested, sothat we can still use it while we don't have junit.WDYT?
In the meanwhile I will create an integration branch, and start to create a list of patches thatcan be merged to core-updates.Where should I send those?
|[Prev in Thread]||Current Thread||[Next in Thread]|