[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=12734436#comment-12734436 ] 

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

OP behind the salesforce reference here.

As to what concerning the "workaround which works fine"

To resolve for this precedence issue, I followed the trick detailed in [1], meaning:
Right click on Project -> Build Path -> Configure Build Path... -> then "Order and Export" tab --> move JRE System Library below the Maven dependencies.

In such a way to have the .classpath file modified to suit ordering as:
1. Maven
2. JRE

In such a way the javax.annotation.Resource will be taken from JavaEE6 libraries instead of the JavaSE Runtime Environment.

But I agree with the [1] comment author, it seems a dirty approach. 

Thank you very much,
Ciao,
Matteo
[1] https://community.jboss.org/wiki/HackingAS7UsingEclipse#comment-7955
                
> 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