Home » Language IDEs » AspectJ » UpdateJob Exception
| UpdateJob Exception [message #46486] |
Tue, 18 January 2005 10:25  |
Eclipse User |
|
|
|
Hi
I'm using Eclipse 3.01 on Windows 2000 and continually get the following
error when I rename items:
!ENTRY org.eclipse.core.runtime 4 2 Jan 18, 2005 09:37:15.977
!MESSAGE An internal error occurred during: "Build configuration update".
!STACK 0
java.lang.NullPointerException
at
org.eclipse.ajdt.buildconfigurator.UpdateJob.fileMoved(Updat eJob.java:174)
at org.eclipse.ajdt.buildconfigurator.UpdateJob.run(UpdateJob.j ava:89)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
It doesn't seemt to cause any problems, but I'd like to track down the
nature of the exception.
TIA
Nick
|
|
|
| Re: UpdateJob Exception [message #46542 is a reply to message #46486] |
Tue, 18 January 2005 11:18  |
| Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
On Tue, 18 Jan 2005 15:25:55 +0000, Nick Wadge wrote:
> I'm using Eclipse 3.01 on Windows 2000 and continually get the following
> error when I rename items:
>
> !ENTRY org.eclipse.core.runtime 4 2 Jan 18, 2005 09:37:15.977 !MESSAGE An
> internal error occurred during: "Build configuration update". !STACK 0
> java.lang.NullPointerException
> at
> org.eclipse.ajdt.buildconfigurator.UpdateJob.fileMoved(Updat eJob.java:174)
> at org.eclipse.ajdt.buildconfigurator.UpdateJob.run(UpdateJob.j ava:89) at
> org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> It doesn't seemt to cause any problems, but I'd like to track down the
> nature of the exception.
Which version of AJDT are you using? The line number from the stack trace
doesn't match with the latest source.
Also, what is the name of the file you are renaming, and which rename
operation are you using, Rename from the resource perspective, or Refactor
> Rename from JDT?
Regards,
Matt.
|
|
|
| Re: UpdateJob Exception [message #46569 is a reply to message #46542] |
Wed, 19 January 2005 04:32 |
| Eclipse User |
|
|
|
Matt Chapman wrote:
> On Tue, 18 Jan 2005 15:25:55 +0000, Nick Wadge wrote:
>> I'm using Eclipse 3.01 on Windows 2000 and continually get the following
>> error when I rename items:
>>
>> !ENTRY org.eclipse.core.runtime 4 2 Jan 18, 2005 09:37:15.977 !MESSAGE An
>> internal error occurred during: "Build configuration update". !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ajdt.buildconfigurator.UpdateJob.fileMoved(Updat eJob.java:174)
>> at org.eclipse.ajdt.buildconfigurator.UpdateJob.run(UpdateJob.j ava:89) at
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>>
>> It doesn't seemt to cause any problems, but I'd like to track down the
>> nature of the exception.
> Which version of AJDT are you using? The line number from the stack trace
> doesn't match with the latest source.
> Also, what is the name of the file you are renaming, and which rename
> operation are you using, Rename from the resource perspective, or Refactor
>> Rename from JDT?
> Regards,
> Matt.
I'm not specifically using AJDT at all. I'm using the Java Browsing
perspective and selecting the Refactor/Rename option from the Types view.
It happens on all types. I've no idea where AJDT comes in to it, however
the plugin version is 1.2.0.20041013155315.
Many thanks
Nick
|
|
| |
| Re: UpdateJob Exception [message #46617 is a reply to message #46595] |
Wed, 19 January 2005 13:03 |
| Eclipse User |
|
|
|
Matt Chapman wrote:
> On Wed, 19 Jan 2005 09:32:47 +0000, Nick Wadge wrote:
>> I'm not specifically using AJDT at all. I'm using the Java Browsing
>> perspective and selecting the Refactor/Rename option from the Types view.
>> It happens on all types. I've no idea where AJDT comes in to it, however
>> the plugin version is 1.2.0.20041013155315.
> Nick,
> Thanks for the extra information. You have AJDT 1.2.0M1 installed, and
> you've hit bug 77179, which has been fixed in AJDT 1.2.0M2. We have a
> resource change listener which was picking up changes in non-AspectJ
> projects. You can safely ignore the exception, or upgrade to AJDT 1.2.0M2
> and it will go away.
> Regards,
> Matt.
The upgrade has solved it. Thanks very much for your help.
Nick
|
|
|
| Re: UpdateJob Exception [message #585995 is a reply to message #46486] |
Tue, 18 January 2005 11:18 |
| Eclipse User |
|
|
|
On Tue, 18 Jan 2005 15:25:55 +0000, Nick Wadge wrote:
> I'm using Eclipse 3.01 on Windows 2000 and continually get the following
> error when I rename items:
>
> !ENTRY org.eclipse.core.runtime 4 2 Jan 18, 2005 09:37:15.977 !MESSAGE An
> internal error occurred during: "Build configuration update". !STACK 0
> java.lang.NullPointerException
> at
> org.eclipse.ajdt.buildconfigurator.UpdateJob.fileMoved(Updat eJob.java:174)
> at org.eclipse.ajdt.buildconfigurator.UpdateJob.run(UpdateJob.j ava:89) at
> org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>
> It doesn't seemt to cause any problems, but I'd like to track down the
> nature of the exception.
Which version of AJDT are you using? The line number from the stack trace
doesn't match with the latest source.
Also, what is the name of the file you are renaming, and which rename
operation are you using, Rename from the resource perspective, or Refactor
> Rename from JDT?
Regards,
Matt.
|
|
|
| Re: UpdateJob Exception [message #586013 is a reply to message #46542] |
Wed, 19 January 2005 04:32 |
| Eclipse User |
|
|
|
Matt Chapman wrote:
> On Tue, 18 Jan 2005 15:25:55 +0000, Nick Wadge wrote:
>> I'm using Eclipse 3.01 on Windows 2000 and continually get the following
>> error when I rename items:
>>
>> !ENTRY org.eclipse.core.runtime 4 2 Jan 18, 2005 09:37:15.977 !MESSAGE An
>> internal error occurred during: "Build configuration update". !STACK 0
>> java.lang.NullPointerException
>> at
>> org.eclipse.ajdt.buildconfigurator.UpdateJob.fileMoved(Updat eJob.java:174)
>> at org.eclipse.ajdt.buildconfigurator.UpdateJob.run(UpdateJob.j ava:89) at
>> org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
>>
>> It doesn't seemt to cause any problems, but I'd like to track down the
>> nature of the exception.
> Which version of AJDT are you using? The line number from the stack trace
> doesn't match with the latest source.
> Also, what is the name of the file you are renaming, and which rename
> operation are you using, Rename from the resource perspective, or Refactor
>> Rename from JDT?
> Regards,
> Matt.
I'm not specifically using AJDT at all. I'm using the Java Browsing
perspective and selecting the Refactor/Rename option from the Types view.
It happens on all types. I've no idea where AJDT comes in to it, however
the plugin version is 1.2.0.20041013155315.
Many thanks
Nick
|
|
|
| Re: UpdateJob Exception [message #586030 is a reply to message #46569] |
Wed, 19 January 2005 09:25 |
| Eclipse User |
|
|
|
On Wed, 19 Jan 2005 09:32:47 +0000, Nick Wadge wrote:
> I'm not specifically using AJDT at all. I'm using the Java Browsing
> perspective and selecting the Refactor/Rename option from the Types view.
> It happens on all types. I've no idea where AJDT comes in to it, however
> the plugin version is 1.2.0.20041013155315.
Nick,
Thanks for the extra information. You have AJDT 1.2.0M1 installed, and
you've hit bug 77179, which has been fixed in AJDT 1.2.0M2. We have a
resource change listener which was picking up changes in non-AspectJ
projects. You can safely ignore the exception, or upgrade to AJDT 1.2.0M2
and it will go away.
Regards,
Matt.
|
|
|
| Re: UpdateJob Exception [message #586046 is a reply to message #46595] |
Wed, 19 January 2005 13:03 |
| Eclipse User |
|
|
|
Matt Chapman wrote:
> On Wed, 19 Jan 2005 09:32:47 +0000, Nick Wadge wrote:
>> I'm not specifically using AJDT at all. I'm using the Java Browsing
>> perspective and selecting the Refactor/Rename option from the Types view.
>> It happens on all types. I've no idea where AJDT comes in to it, however
>> the plugin version is 1.2.0.20041013155315.
> Nick,
> Thanks for the extra information. You have AJDT 1.2.0M1 installed, and
> you've hit bug 77179, which has been fixed in AJDT 1.2.0M2. We have a
> resource change listener which was picking up changes in non-AspectJ
> projects. You can safely ignore the exception, or upgrade to AJDT 1.2.0M2
> and it will go away.
> Regards,
> Matt.
The upgrade has solved it. Thanks very much for your help.
Nick
|
|
|
Goto Forum:
Current Time: Fri Jun 20 00:54:46 EDT 2025
Powered by FUDForum. Page generated in 0.07159 seconds |
Home