Skip to main content



      Home
Home » Eclipse Projects » Equinox » Is the eclipse registry presistent?
Is the eclipse registry presistent? [message #80117] Thu, 04 January 2007 20:49 Go to next message
Eclipse UserFriend
I had a typo in my plugin.xml for a classname. The result was an error
message when I tried to used the extension point: class not found. I
fixed the typo. But the error did not go away.

I tried several times, thinking I wasn't really saving the plugin.xml or
something.

Finally I recalled that equinox recovers plugin startup status. Could it
also be saving the registration of plugin.xml files between application
launches? So I cleared the workspace data when I launched the PDE
application. Fixed.

Of course clearing the workspace data also erased all of my workspace
state, so I'd rather not do that again.

So did clearing the workspace data cause the persistent registry to be
cleared or is there no such thing?

Thanks,
John.
Re: Is the eclipse registry presistent? [message #80132 is a reply to message #80117] Fri, 05 January 2007 02:17 Go to previous messageGo to next message
Eclipse UserFriend
JOHN J. BARTON wrote:
> Finally I recalled that equinox recovers plugin startup status. Could it
> also be saving the registration of plugin.xml files between application
> launches? So I cleared the workspace data when I launched the PDE
> application. Fixed.

The startup parameter "-clean" should be all you need.

See here:
http://help.eclipse.org/help32/index.jsp?topic=/org.eclipse. platform.doc.user/tasks/running_eclipse.htm

Cu, Gunnar

--
Gunnar Wagenknecht
gunnar@wagenknecht.org
http://wagenknecht.org/
Re: Is the eclipse registry presistent? [message #80235 is a reply to message #80117] Fri, 05 January 2007 10:36 Go to previous message
Eclipse UserFriend
Hi John,
It looks like you re-discovered this bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=104267

The problem has been fixed in Eclipse 3.3 M1.

To summarize the most typical use case in it: changes to plugin.xml made
while debug session is running are not going to be picked up in the
subsequent runs.

As Gunnar pointed out, the workaround is to use "-clean" if you are running
from outside of PDE, or you can modify the PDE launch configuration to do it
for you:

- Open debug / run configuration (depending if you do debug or run)
- Switch to the "Configuration" tab
- Select "Clear the configuration area before launching"

To answer your question, the Eclipse registry is cached to improve startup
speed. The cache is cleared when OSGi state changes or a timestamp on one of
the plugin.xml files changes (dev mode only). However, prior to this fix
timestamps were calculated on Eclipse shutdown rather when at the time
content of the plugin.xml was consumed.

Sincerely,
Oleg Besedin

"JOHN J. BARTON" <johnjbarton@johnjbarton.com> wrote in message
news:enkart$ojo$1@utils.eclipse.org...
>I had a typo in my plugin.xml for a classname. The result was an error
>message when I tried to used the extension point: class not found. I fixed
>the typo. But the error did not go away.
>
> I tried several times, thinking I wasn't really saving the plugin.xml or
> something.
>
> Finally I recalled that equinox recovers plugin startup status. Could it
> also be saving the registration of plugin.xml files between application
> launches? So I cleared the workspace data when I launched the PDE
> application. Fixed.
>
> Of course clearing the workspace data also erased all of my workspace
> state, so I'd rather not do that again.
>
> So did clearing the workspace data cause the persistent registry to be
> cleared or is there no such thing?
>
> Thanks,
> John.
Previous Topic:Running Equinox as a standalone application
Next Topic:Exception Starting Unresolved Bundles
Goto Forum:
  


Current Time: Sun Jul 06 14:40:17 EDT 2025

Powered by FUDForum. Page generated in 0.03594 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top