[
http://team.ops4j.org/browse/QI-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17826#comment-17826
]
Paul Merlin commented on QI-369:
--------------------------------
Gang,
Problem spotted: classes.getDeclaredMethod() always advertised that the method
order cannot be predicted but until now it was source order.
Now with JDK7 the method order is random.
About all DCI-Cargo tests relies on methods order, ie. tests are not
independents, that's why they fail randomly.
I'll try to enforce their order as a quick fix ... don't know yet how I'll do
that though, probably case by case.
Related changes were done in JUnit but not released yet ...
See:
- https://github.com/KentBeck/junit/pull/293
- https://github.com/KentBeck/junit/pull/440
Next JUnit version will provide predictible test order but hard to game with.
The test order will be based on test method name hashcodes.
To be continued
/Paul
> Make the Qi4j SDK compile on jdk7
> ---------------------------------
>
> Key: QI-369
> URL: http://team.ops4j.org/browse/QI-369
> Project: Qi4j
> Issue Type: Improvement
> Reporter: Paul Merlin
> Fix For: 2.0 - Reductionism
>
>
> Qi4j fails to compile using jdk7.
> We should stick with jdk6 for now but making it compile on jdk7 to minimize
> future surprises.
> Doing it for 2.0 will prevent eventual breaking changes.
> A disabled job is ready on the continuous integration and will be activated
> when work is started on this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://team.ops4j.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
