Optimize CandidateChecks and exclude java.lang and groovy.lang
Reported by me (at andresteingress) | March 31st, 2011 @ 09:23 AM | in 1.2.1
In order to exclude more packages from ContractElement checking, we should take groovy.lang and java.lang out in CandidateChecks.
Comments and changes to this ticket
-
me (at andresteingress) March 31st, 2011 @ 09:37 AM
(from [c583766f26ba81dccc0df54d219ad6be7092d22e]) Optimize CandidateChecks and exclude java.lang and groovy.lang [#12] https://github.com/andresteingress/gcontracts/commit/c583766f26ba81...
-
me (at andresteingress) March 31st, 2011 @ 09:38 AM
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
core module
People watching this ticket
me (at andresteingress)
Referenced by
-
12
Optimize CandidateChecks and exclude java.lang and groovy.lang
(from [c583766f26ba81dccc0df54d219ad6be7092d22e])
Optimiz...