[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Removing access restrictions on classes.jar

Nope.  Was a Maven project, using the Maven plugin.  Don't know why on earth things got messed up during the upgrade.   The Ganymede maven plugin stuff is a bit more paternalistic than the old one.

Thanks for the response... :)

On Jul 23, 2008, at 2:18 PM, Thomas Watson wrote:

Hi Hal,

Is the project a PDE project? If so then this could happen when you set the Bundle-ExecutionEnvironment header in your bundle manifest and have PDE update your classpath settings. This will apply an execution environment definition to your VM to prevent you from accessing packages which are not in one of the defined EEs (e.g. J2SE-1.4 execution environment does not contain sun.* classes).

You can actually remove these access rules by going to the projects Properties->Java Build Path->Libraries tab and selecting the JRE System Library to edit. Instead of using an Execution Environment you can use an Alternative JRE that does not use an Execution Environment definition.

Tom



<graycol.gif>Hal Hildebrand ---07/23/2008 01:40:28 PM---Okay, figured out this is due to some odd change to a restricted development environment form the

<ecblank.gif>
From:
<ecblank.gif>
Hal Hildebrand <hal.hildebrand@xxxxxxxxxx>
<ecblank.gif>
To:
<ecblank.gif>
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
<ecblank.gif>
Date:
<ecblank.gif>
07/23/2008 01:40 PM
<ecblank.gif>
Subject:
<ecblank.gif>
Re: [equinox-dev] Removing access restrictions on classes.jar





Okay, figured out this is due to some odd change to a restricted  
development environment form the workspace defined JRE.  Not sure how  
that happened, but frightening non-the-less.

Sorry for the spam.

On Jul 23, 2008, at 11:27 AM, Hal Hildebrand wrote:

> Sorry for asking the development list, but I'm at my wit's end.
>
> I upgraded to Ganymede and now I have *#@**@ access restrictions on  
> my JRE 1.5 classes.jar.  These access restrictions are marked as  
> unmodifiable - and low and behold they are unmodifiable.  I am using  
> a class in sun.* and this worked fine in the previous version of  
> Eclipse.
>
> First, can someone please - dear god, please - help me overcome this  
> problem.
>
> Second, why are these *unmodifiable*?
>
> Third, when did this work in previous versions but now bangs me on  
> the head in Ganymede
>
> Thanks
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev