Hello Igor, thank you for your answer.
On Thu, Nov 10, 2011 at 5:35 PM, Igor Fedorenko <[email protected]> wrote: > AFAIK, there is no nice solution and I think this is general Maven > limitation. Bugzilla [1] talks about the same problems and for command > line build the solution appears to be use of endorsed libraries. You > maybe able to workaround the problem by adding > jboss-annotations-api_1.1_spec to JRE classpath using "Installed JREs" > workspace preference page. I found the endorsed lib solution working for the command line build. Inside the eclipse, adding the jar to the JRE lib works. But I think this is a kind of local hack: not portable and problematic when having many different projects. > [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=363237 Is there a plan to implement the suggested feature from the bugzilla comment, to not reorder the eclipse project libraries settings? Moving the maven dependencies before the JRE lib works fine until m2e resets the order. Regards, Lars _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
