Same problem for me, and this is a real issue.

m2eclipse allow us to have not anymore .project and .classpath in SCM,
it would be a big problem if we had to commit these file again.

My suggestion should be to do exactly what Eclipse do when we add Java
library : allow access to all classes by defining no access rules : no
forbidden, no accessible.

On Fri, Nov 7, 2008 at 1:21 AM, Eugene Kuleshov <[EMAIL PROTECTED]> wrote:
> Pat,
>
>  This is currently not supported by m2eclipse. More over, this info is not
> represented in the Maven's pom.xml, which makes this tricky to do it
> automatically.
>
>  Perhaps one option for m2eclipse would be to use .project and .classpath
> when importing Maven projects (including projects checked out from svn),
> then you could do that just once and we can preserve this setting when
> running "Maven / Update project" action.
>
>  Do you have other ideas or suggestions how to deal with this issue?
>
>  regards,
>  Eugene
>
>
> stug23 wrote:
>>
>> When using Sun's sun.misc.BASE64Decoder, Eclipse shows an error which
>> requires configuring an access rule via the Eclipse UI -- this ends up
>> creating an <accessrule/> tag in the Eclipse .classpath file as shown
>> below.
>>
>> How can I configure my pom.xml such that when checking out the related
>> Maven
>> project from Subversion, this access rule will be added to the Eclipse
>> .classpath file without having to store the .classpath file in Subversion?
>>
>> ====
>> <classpathentry kind="con"
>>
>> path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/J2SE-1.5">
>>   <accessrules>
>>      <accessrule kind="accessible" pattern="sun/misc/**"/>
>>   </accessrules>
>> </classpathentry>
>> ====
>>
>
> ---------------------------------------------------------------------
> 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


Reply via email to