[ https://issues.jboss.org/browse/WELD-1111?page=com.atlassian.jira.plugin.... ] Martin Kouba commented on WELD-1111: ------------------------------------ See also TCK 1.1 test: *org.jboss.cdi.tck.tests.inheritance.generics.MemberLevelInheritanceTest* -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-1111?page=com.atlassian.jira.plugin.... ] Marko Lukša updated WELD-1111: ------------------------------ Git Pull Request: https://github.com/weld/core/pull/193 This is now fixed for injection points in beans, but still needs to be fixed for injection points in {{InjectionTarget}}s created through {{BeanManager.createInjectionTarget()}}. Currently, {{InjectionPoint}} does not have a reference to the {{AnnotatedType}} used for creating the {{InjectionTarget}} (it only has a reference to the {{Bean}}, but since there's no {{Bean}} here, we don't have the necessary info to resolve any type variables in the type of the injected field). Martin, maybe you should expand the TCK tests to also check for additional injection point types that must also be resolved according to the spec. Take a look at {{org.jboss.weld.tests.unit.reflection.inheritance.TypeVariableResolverTest}}. Weld should handle all these tricky injection point types, but probably the TCK should also check this? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-1111?page=com.atlassian.jira.plugin.... ] Ales Justin updated WELD-1111: ------------------------------ Fix Version/s: 1.1.8.Final Git Pull Request: https://github.com/weld/core/pull/193 (was: https://github.com/weld/core/pull/193) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-1111?page=com.atlassian.jira.plugin.... ] Ales Justin resolved WELD-1111. ------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-1111?page=com.atlassian.jira.plugin.... ] Marko Lukša commented on WELD-1111: ----------------------------------- Ron, yes, you're right. Initially the test started out as an integration test, but I later realized I could strip it down to simply test TypeVariableResolver directly, but forgot to move it. I'll move it to the correct location when I fix the failing test (there's a new jira task for it: WELD-1127) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/WELD-1111?page=com.atlassian.jira.plugin.... ] Jozef Hartinger updated WELD-1111: ---------------------------------- Fix Version/s: 2.0.0.Alpha3 Git Pull Request: https://github.com/weld/core/pull/193 (was: https://github.com/weld/core/pull/193) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira