[jbosstools-issues] [JBoss JIRA] (JBIDE-13074) The attribute lookup is undefined for the annotation type Resource.

[Matteo Mortari (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-13074?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735162#comment-12735162 ] 

Matteo Mortari commented on JBIDE-13074:
----------------------------------------

OP behind the salesforce reference here.

Thank you for the information this issue will be fixed in JBDS 6.

Thank you as well for having attached the required POM. I also tried to follow the instructions on [1] but got stuck on the full modification of the POM to mark goal as ignored.

Considering all these info, I'm actually more happier to just use the "Order and Export" tab, and to try this POM modification only if I will eventually find myself performing this manual operation too many times.

I'm happy for you to close this JIRA in relation to the JBDS 6 release, you provided all information of possible workarounds which satisfy my original enquiry. Thank you
Ciao,
Matteo

[1] http://jaitechwriteups.blogspot.fr/2011/02/resource-and-new-lookup-attribute-how.html
                
> The attribute lookup is undefined for the annotation type Resource. 
> --------------------------------------------------------------------
>
>                 Key: JBIDE-13074
>                 URL: https://issues.jboss.org/browse/JBIDE-13074
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>            Reporter: Gary Hu
>            Assignee: Fred Bricon
>
> The attribute "lookup" is not recognized by JBDS 5 for the annotation @Resource.  
> To reproduce the issue, 
> 1) import cdi-injection quickstart into JBDS 5.0.1 as a maven project.
> 2) run maven build "eclipse:eclipse" from JBDS. 
> 3) open EnglishTranslateService.java and add the annotation @Resource(lookup="")
> It will shows the message "the attribute lookup is undefined for the annotation type Resource".
> This issue is raised in the wiki [1] in the section "Correct build path precedence errors".
> It seems that it's related to the eclipse bug [2].
> The wiki provides a workaround which works fine. However, can we provide a complete and clean fix from JBDS side?
> [1] https://community.jboss.org/wiki/HackingAS7UsingEclipse
> [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=342128

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira