[weld-issues] [JBoss JIRA] (CDITCK-582) BeanDiscoveryTest causes AmbiguousResolutionException

2017-05-30 Thread Martin Kouba (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Martin Kouba commented on  CDITCK-582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BeanDiscoveryTest causes AmbiguousResolutionException   
 

  
 
 
 
 

 
 I think it was added due to backward compatibility but I don't remember the details.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-582) BeanDiscoveryTest causes AmbiguousResolutionException

2017-05-30 Thread Tomas Remes (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomas Remes resolved as Rejected  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-582  
 
 
  BeanDiscoveryTest causes AmbiguousResolutionException   
 

  
 
 
 
 

 
Change By: 
 Tomas Remes  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Rejected  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-582) BeanDiscoveryTest causes AmbiguousResolutionException

2017-05-30 Thread Mark Struberg (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Struberg commented on  CDITCK-582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BeanDiscoveryTest causes AmbiguousResolutionException   
 

  
 
 
 
 

 
 Ouch this is this weirdo rule that jars which contain an Extension are not implicit BDAs  Yes, while I personally find this rule extremely weird, it nonetheless does exist. Ok to reject.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-582) BeanDiscoveryTest causes AmbiguousResolutionException

2017-05-30 Thread Tomas Remes (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tomas Remes commented on  CDITCK-582  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BeanDiscoveryTest causes AmbiguousResolutionException   
 

  
 
 
 
 

 
 I think the LegacyAlpha is added only once using addAnnotatedType. Note that the JavaArchive (where this class resides) is not a bean archive because it doesn't contain beans.xml file and it does contain an extension.  This test is quite old and I consider it ok so I am about to reject this issue.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.3#72005-sha1:73be91d)  
 
 

 
   
 

  
 

  
 

   

___
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues

[weld-issues] [JBoss JIRA] (CDITCK-582) BeanDiscoveryTest causes AmbiguousResolutionException

2017-05-30 Thread Mark Struberg (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Struberg created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 CDI TCK /  CDITCK-582  
 
 
  BeanDiscoveryTest causes AmbiguousResolutionException   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.0.0.Final  
 
 
Assignee: 
 Tomas Remes  
 
 
Components: 
 Tests  
 
 
Created: 
 30/May/17 7:23 AM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Mark Struberg  
 

  
 
 
 
 

 
 BeanDiscoveryTest has a @RequestScoped LegacyAlpha bean plus it adds the AnnotatedType (without any change) via an Extension.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment