[ https://issues.jboss.org/browse/JBIDE-13074?page=com.atlassian.jira.plugi... ] 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 -- 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

[ https://issues.jboss.org/browse/JBIDE-13074?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-13074 at 11/15/12 4:40 AM: --------------------------------------------------------------- This is actually covered by JBIDE-11738. If you follow the workaround described in http://jaitechwriteups.blogspot.fr/2011/02/resource-and-new-lookup-attrib... you just need to : * add a <phase> to the maven-dependency-plugin execution. This is a small bug we'll fix in JBDS 6 CR1 * right-click on project Maven > Update Project Configuration * you might see an error marker on the maven-plugin-compiler plugin if the endorsed lib folder doesn't exist, you can quick fix it http://screencast.com/t/xRjuLJZaYHga * also quick fix the maven-dependency-plugin error ("plugin execution not covered"), to mark the goal as ignored in your pom.xml. In [JBDS 6.0|https://devstudio.jboss.com/earlyaccess/], m2e 1.2 will be installed, so you'll be able to do that on a workspace level instead. So your pom.xml should look like : {noformat} <plugins> ... <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>${version.compiler.plugin}</version> <configuration> <source>${maven.compiler.source}</source> <target>${maven.compiler.target}</target> <compilerArgument>-Djava.endorsed.dirs=${project.build.directory}/endorsed</compilerArgument> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.5</version> <configuration> <!-- Setup the surefire plugin to use the endorsed directory containing the jar for javax.annotation.* classes. Remember that we setup this folder via the maven-dependency-plugin configuration, above. --> <argLine>-Djava.endorsed.dirs=${project.build.directory}/endorsed</argLine> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.1</version> <executions> <execution> <phase>validate</phase> <goals> <goal>copy</goal> </goals> <configuration> <!-- Configure the plugin to copy the jar containing javax.annotation.* to a folder named "endorsed" within the project's build directory --> <artifactItems> <artifactItem> <groupId>org.jboss.spec.javax.annotation</groupId> <artifactId>jboss-annotations-api_1.1_spec</artifactId> </artifactItem> </artifactItems> <outputDirectory>${project.build.directory}/endorsed</outputDirectory> </configuration> </execution> </executions> </plugin> ... </plugins> ... <pluginManagement> <plugins> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.--> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId> org.apache.maven.plugins </groupId> <artifactId> maven-dependency-plugin </artifactId> <versionRange> [2.1,) </versionRange> <goals> <goal>copy</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> {noformat} was (Author: fbricon): This is actually covered by JBIDE-11738. If you follow the workaround described in http://jaitechwriteups.blogspot.fr/2011/02/resource-and-new-lookup-attrib... you just need to : * add a <phase> to the maven-dependency-plugin execution. This is a small bug we'll fix in JBDS 6 CR1 * right-click on project Maven > Update Project Configuration * you might see an error marker on the maven-plugin-compiler plugin if the endorsed lib folder doesn't exist, you can quick fix it http://screencast.com/t/xRjuLJZaYHga * also quick fix the maven-dependency-plugin error ("plugin execution not covered"), to mark the goal as ignored in your pom.xml. In [https://devstudio.jboss.com/earlyaccess/ JBDS 6.0], m2e 1.2 will be installed, so you'll be able to do that on a workspace level instead. So your pom.xml should look like : {noformat} <plugins> ... <plugin> <artifactId>maven-compiler-plugin</artifactId> <version>${version.compiler.plugin}</version> <configuration> <source>${maven.compiler.source}</source> <target>${maven.compiler.target}</target> <compilerArgument>-Djava.endorsed.dirs=${project.build.directory}/endorsed</compilerArgument> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <version>2.5</version> <configuration> <!-- Setup the surefire plugin to use the endorsed directory containing the jar for javax.annotation.* classes. Remember that we setup this folder via the maven-dependency-plugin configuration, above. --> <argLine>-Djava.endorsed.dirs=${project.build.directory}/endorsed</argLine> </configuration> </plugin> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.1</version> <executions> <execution> <phase>validate</phase> <goals> <goal>copy</goal> </goals> <configuration> <!-- Configure the plugin to copy the jar containing javax.annotation.* to a folder named "endorsed" within the project's build directory --> <artifactItems> <artifactItem> <groupId>org.jboss.spec.javax.annotation</groupId> <artifactId>jboss-annotations-api_1.1_spec</artifactId> </artifactItem> </artifactItems> <outputDirectory>${project.build.directory}/endorsed</outputDirectory> </configuration> </execution> </executions> </plugin> ... </plugins> ... <pluginManagement> <plugins> <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.--> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</artifactId> <version>1.0.0</version> <configuration> <lifecycleMappingMetadata> <pluginExecutions> <pluginExecution> <pluginExecutionFilter> <groupId> org.apache.maven.plugins </groupId> <artifactId> maven-dependency-plugin </artifactId> <versionRange> [2.1,) </versionRange> <goals> <goal>copy</goal> </goals> </pluginExecutionFilter> <action> <ignore></ignore> </action> </pluginExecution> </pluginExecutions> </lifecycleMappingMetadata> </configuration> </plugin> </plugins> </pluginManagement> {noformat} -- 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

[ https://issues.jboss.org/browse/JBIDE-13074?page=com.atlassian.jira.plugi... ] 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-attrib... -- 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