| [Help Eclipse 2.1.1]:IResourceDeltaVisitor#visit(IResourceDelta res) not called when saving the reso [message #95669] |
Mon, 15 September 2003 07:51  |
Eclipse User |
|
|
|
Originally posted by: francis.andre.easynet.fr
Hi everybody
I got a tedious problem with the IResourceDeltaVisitor with a local plugin.
When I debug the plugin under Eclipse 2.1.1 as a Run-time Workbench plugin ,
everything is fine, i.e, a save fo the resource leads to a call to
IResourceDeltaVisitor#visit(IResourceDelta delta). But when I restart
Eclipse after having installed the plugin as a external plugin, the
IResourceDeltaVisitor#visit is never called. It is like if the keystrokes
CNTRL-s was dropped or bypassed and never seen by the platform???
Any idea where I could check what's happening or what could be the reason of
this incoherent behavior???
I have to mention that I have the same problem with JDT
Regards
FA
|
|
|
|
| Re: [Help Eclipse 2.1.1]:IResourceDeltaVisitor#visit(IResourceDelta res) not called when saving the [message #96160 is a reply to message #96060] |
Tue, 16 September 2003 03:13  |
| Eclipse User |
|
|
|
Originally posted by: francis.andre.easynet.fr
John
I have looked at the error log and everything is fine, there is no message
logged for my plugin.
However, I told in my previous mail that the JDT gets also the same problem.
Let me explain what happing exactly with JDT and may be it give you a
indication on what is the origin of this problem.
1/ Creation of a new class: ok
Under a src directory, I create a new class with a new package name:
com.mypack.Foo. The Java editor popups a editing window as usual with the
following code:
package com.mypack;
class Foo {
}
The class appears normaly in the Package explorer under the
Project/src/com/mypack directory and the tab displays "foo.java".
2/ Modification of the source code by an invalid member definition.
I insert in the class a wrong definition of the member bar with Pippo as
type, i.e,
package com.mypack;
class Foo {
Pippo bar;
}
At that point,
a) a error marker appears in the front of the declaration of Pippo bar
saying that Pippo is not a valid type for the field
Foo.a: that's ok
b) the "Foo.java" tab gets the asterisk meaning that the source Foo.java
has been modified: that'ok
3/ Saving of the erroneous source code of Foo.java
Here are comming the problems. When I save the source code by typing CNTRL-s
a) the "*" marker on the Foo.java tab disappears: that's ok
b) BUT the error message is NOT displayed in the Tasks window and there
is no error marker appearing neither in the Package explorer on the package
com.mypack element, neither on the class element Foo.java: that's NOT ok
4/ Correcting the faulty definition of Foo.bar
When I correct the definition of Foo.bar from
Pippo bar;
to
int bar;
a) the error marker in the editor window disappears: that'ok
b) but the class is NOT generated in the corresponding "bin" directory
of the project
5/ Building the project:
I rollback the "bar" declaration to the erroneous definition of "Pippo
bar". And when I Build the project, all out-of-date files are recompiled
including Foo.java and at this point, all the "red" error markers for
Foo.java are appearing at their respective "rigth" place i.e.
a) On the package element in the PackageExplorer
b) On the Java element "Foo.java" in the PackageExplorer
c) In the Tasks window
What's wrong with JDT???
Regards
PS: I do not think it is related to this problem, but I just want to mention
that my plugin and the JDT plugin were working fine with Eclipse before
I changed my hardware configuration from a Pentium IV 1.5 Ghz/512 Mb to
a P IV 2.6 Ghz HtypeThreading/1 Gb
I changed from Eclipse 2.0 to 2.1.1
"John Arthorne" <John_Arthorne@oti.com_> a
|
|
|
| Re: [Help Eclipse 2.1.1]:IResourceDeltaVisitor#visit(IResourceDelta res) not called when saving the [message #96216 is a reply to message #96160] |
Tue, 16 September 2003 05:54 |
| Eclipse User |
|
|
|
It sounds like you're not in auto-build mode.
Jerome
"Francis ANDRE" <francis.andre@easynet.fr> wrote in message
news:bk6d4a$ni2$1@eclipse.org...
> John
>
> I have looked at the error log and everything is fine, there is no message
> logged for my plugin.
>
> However, I told in my previous mail that the JDT gets also the same
problem.
> Let me explain what happing exactly with JDT and may be it give you a
> indication on what is the origin of this problem.
>
>
>
> 1/ Creation of a new class: ok
> Under a src directory, I create a new class with a new package name:
> com.mypack.Foo. The Java editor popups a editing window as usual with the
> following code:
>
> package com.mypack;
>
> class Foo {
> }
>
> The class appears normaly in the Package explorer under the
> Project/src/com/mypack directory and the tab displays "foo.java".
>
>
>
>
> 2/ Modification of the source code by an invalid member definition.
> I insert in the class a wrong definition of the member bar with Pippo as
> type, i.e,
>
> package com.mypack;
>
> class Foo {
> Pippo bar;
> }
>
> At that point,
> a) a error marker appears in the front of the declaration of Pippo bar
> saying that Pippo is not a valid type for the field
> Foo.a: that's ok
> b) the "Foo.java" tab gets the asterisk meaning that the source
Foo.java
> has been modified: that'ok
>
>
>
>
>
> 3/ Saving of the erroneous source code of Foo.java
> Here are comming the problems. When I save the source code by typing
CNTRL-s
> a) the "*" marker on the Foo.java tab disappears: that's ok
> b) BUT the error message is NOT displayed in the Tasks window and
there
> is no error marker appearing neither in the Package explorer on the
package
> com.mypack element, neither on the class element Foo.java: that's NOT ok
>
>
>
>
> 4/ Correcting the faulty definition of Foo.bar
> When I correct the definition of Foo.bar from
> Pippo bar;
> to
> int bar;
>
> a) the error marker in the editor window disappears: that'ok
> b) but the class is NOT generated in the corresponding "bin" directory
> of the project
>
>
>
> 5/ Building the project:
> I rollback the "bar" declaration to the erroneous definition of "Pippo
> bar". And when I Build the project, all out-of-date files are recompiled
> including Foo.java and at this point, all the "red" error markers for
> Foo.java are appearing at their respective "rigth" place i.e.
> a) On the package element in the PackageExplorer
> b) On the Java element "Foo.java" in the PackageExplorer
> c) In the Tasks window
>
>
> What's wrong with JDT???
>
>
> Regards
>
>
> PS: I do not think it is related to this problem, but I just want to
mention
> that my plugin and the JDT plugin were working fine with Eclipse before
> I changed my hardware configuration from a Pentium IV 1.5 Ghz/512 Mb
to
> a P IV 2.6 Ghz HtypeThreading/1 Gb
> I changed from Eclipse 2.0 to 2.1.1
>
>
> "John Arthorne" <John_Arthorne@oti.com_> a
|
|
|
Powered by
FUDForum. Page generated in 0.26443 seconds
Home