[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[Subclipse-users] Plugin "Notifications" between Spring IDE & Subclipse

From: Zach Bailey <zach.bailey_at_hannonhill.com>
Date: 2007-08-29 16:54:19 CEST

Hi all,

Just a conceptual question here. I have a plugin (SpringIDE 2.0.1 to be
exact) that doesn't seem to be playing nice with Subclipse. Let me
outline the scenario:

1.) Update my working copy, receive changes to Spring Context XML files
as well as Java changes
2.) Project rebuilds due to changes, however Spring files show errors as
if they were not "rebuilt" or "revalidated"

My question here is how exactly is Eclipse and any Plugins in the
environment notified when any given Plugin changes a file. I would
imagine a resource change event is raised or something similar.

*Could this be a case of Subclipse not raising this event properly, or
not in the proper order?

*Could this be a case of the Spring IDE not listening for this event
properly? (obviously this is not really a question for this list, but
one has to assume that Spring IDE handles it correctly since the file is
revalidated upon edit/save)

Perhaps this issue is simply with the order in which these events are
fired, which seems to be effectively out of control of any one plugin.
Does Eclipse expose a functionality for a plugin to specify the order in
which it would like to receive events? (for example, notify me of Java
file changes, then XML file changes) This seems like it would be the
responsibility of the plugin to manage.

Thanks for any insight any plugin authors that read this list could provide.

Cheers,
-Zach

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Aug 29 17:03:09 2007

This is an archived mail posted to the Subclipse Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.