groovy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jochen Theodorou <blackd...@gmx.org>
Subject Re: progress on executing tests with JDK9 status update
Date Thu, 25 Aug 2016 05:29:03 GMT
On 25.08.2016 01:14, John Wagenleitner wrote:
[...]
>         groovy.transform.stc.GenericsSTCTest > testGenericField FAILED
>         org.codehaus.groovy.control.Mu
>         <http://org.codehaus.groovy.control.Mu>ltipleCompilationErrorsException:
>         startup failed:
>              TestScripttestGenericField257.groovy: 2: unable to resolve
>         class javax.xml.ws.Holder
>               @ line 2, column 13.
>                             import javax.xml.ws.Holder
>                             ^
>
>
>     there are 2 of this kind of failure. The problem being that you need
>     access to the module java.xml.ws <http://java.xml.ws> or java.se.ee
>     <http://java.se.ee> to be able to get Holder class. I did not manage
>     to solve this one yet. "org.gradle.jvmargs=-ea -Xmx1G -addmods
>     java.se.ee <http://java.se.ee>" did not fix the failure. Makes me
>     wonder if that is then also used for tests.
>
> I had looked at that and I don't think the
> GenericsSTCTest.testGenericField needs to rely on the java.xml.ws.Holder
> class in order to be an effective test.  I think it could be replaced by
> class defined inline in the assertScript and then the dependency on the
> java.xml module can be eliminated for core tests.

yes, but
(a) what would be a good replacement? It should be nothing like a 
collection. And it should be in java7
(b) won´t we get the same problem with groovy-xml later on?

bye Jochen

Mime
View raw message