I am not sure disabling the access rules is the best solution. If the com.sun.* jars are needed can't they be added as a dependency and added to the Maven Dependencies Classpath container. The if http://jira.codehaus.org/browse/MNGECLIPSE-1218 is implemented the Access Restriction errors will go away.
Timothy _________________________________________________ Timothy G. Rundle Sr ADT - Technology & Integration Specialist Volvo Information Technology c/o Mack Trucks, Inc. 2100 Mack Blvd. Allentown, PA 18105 USA Telephone: +1-610-709-3706 Fax: +1-610-709-3739 E-mail: timothy.run...@volvo.com -----Original Message----- From: Eugene Kuleshov [mailto:e...@md.pp.ru] Sent: Tuesday, March 10, 2009 11:37 PM To: user@m2eclipse.codehaus.org Subject: Re: [m2eclipse-user] Choosing JRE during import Please vote for http://jira.codehaus.org/browse/MNGECLIPSE-1044 The proper way to fix this issue is to create or change the JRE_CONTAINER entry to declare no access restrictions when importing or updating project. It can be also done after the fact from the project properties and .classpath entry will look something like this: <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.d ebug.ui.launcher.StandardVMType/J2SE-1.5"> <accessrules> <accessrule kind="accessible" pattern="**"/> </accessrules> </classpathentry> I meant to look at it (fix should be quite trivial), but haven't gotten into fixing it yet. So, if someone would want to contribute a patch for it it would really help. regards, Eugene ksangani wrote: > eclipse 3.4.1 > m2eclipse 0.9.6 > > How do I choose JRE when I import the project using m2eclipse plugin? > Currently when I import a project m2eclipse chose J2SE-1.5 execution > environment by default. The problem with this is J2SE-1.5 has stricter > access rules for OSGi runtime. My module uses some com.sun.* packages which > are not visible through J2SE-1.5 execution environment. I have to manually > change to Workspace default JRE in order to make compiler happy. > > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email