| erratic behaviour re. obsolete project references [message #54652] |
Thu, 07 July 2005 19:07  |
Eclipse User |
|
|
|
I had the strange case here, that - whenever I rebuilt my project - AJDT
popped up an error telling me
---------------------------------
AspectJ error:
---------------------------------
Error creating marker
reason:
Reource /<other_project>/..../<SomeFile>.java does not exist.
---------------------------------
I indeed previously had "imported" (i.e. referenced) that
<other_project> from my now aspectized current project, but - to improve
the behaviour of the aspect visualizer - in the meantime I now "linked"
the source of <other_project> into my current project (according to the
"Using linked source folders" chapter in the online help), so that
<other_project> should nowhere be referenced any more in the current
project.
But that error kept reappearing each time when I did a rebuild! In the
end I desperately deleted the <other_project> from eclipse (of course
without deleting its content...) and only after that the error popup had
finally gone.
So - apparently - AspectJ keeps around some old reference to a
previously referenced project, even after removing it from the
build-path and obviously that reference even survives (several!) "Build
clean"s.
Michael
|
|
|
| Re: erratic behaviour re. obsolete project references [message #54923 is a reply to message #54652] |
Tue, 12 July 2005 05:46  |
| Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
Hi Macheal,
This is clearly a bug. Please can you raise this in bugzilla, with the
exact steps required to reproduce.
Thanks,
Matt.
On Fri, 08 Jul 2005 01:07:04 +0200, Michael Moser wrote:
> I had the strange case here, that - whenever I rebuilt my project - AJDT
> popped up an error telling me
> ---------------------------------
> AspectJ error:
> ---------------------------------
> Error creating marker
> reason:
> Reource /<other_project>/..../<SomeFile>.java does not exist.
> ---------------------------------
>
> I indeed previously had "imported" (i.e. referenced) that
> <other_project> from my now aspectized current project, but - to improve
> the behaviour of the aspect visualizer - in the meantime I now "linked"
> the source of <other_project> into my current project (according to the
> "Using linked source folders" chapter in the online help), so that
> <other_project> should nowhere be referenced any more in the current
> project.
>
> But that error kept reappearing each time when I did a rebuild! In the
> end I desperately deleted the <other_project> from eclipse (of course
> without deleting its content...) and only after that the error popup had
> finally gone.
>
> So - apparently - AspectJ keeps around some old reference to a
> previously referenced project, even after removing it from the
> build-path and obviously that reference even survives (several!) "Build
> clean"s.
>
> Michael
--
Matt Chapman
AJDT Development, http://www.eclipse.org/ajdt
|
|
|
| Re: erratic behaviour re. obsolete project references [message #589403 is a reply to message #54652] |
Tue, 12 July 2005 05:46 |
| Eclipse User |
|
|
|
Hi Macheal,
This is clearly a bug. Please can you raise this in bugzilla, with the
exact steps required to reproduce.
Thanks,
Matt.
On Fri, 08 Jul 2005 01:07:04 +0200, Michael Moser wrote:
> I had the strange case here, that - whenever I rebuilt my project - AJDT
> popped up an error telling me
> ---------------------------------
> AspectJ error:
> ---------------------------------
> Error creating marker
> reason:
> Reource /<other_project>/..../<SomeFile>.java does not exist.
> ---------------------------------
>
> I indeed previously had "imported" (i.e. referenced) that
> <other_project> from my now aspectized current project, but - to improve
> the behaviour of the aspect visualizer - in the meantime I now "linked"
> the source of <other_project> into my current project (according to the
> "Using linked source folders" chapter in the online help), so that
> <other_project> should nowhere be referenced any more in the current
> project.
>
> But that error kept reappearing each time when I did a rebuild! In the
> end I desperately deleted the <other_project> from eclipse (of course
> without deleting its content...) and only after that the error popup had
> finally gone.
>
> So - apparently - AspectJ keeps around some old reference to a
> previously referenced project, even after removing it from the
> build-path and obviously that reference even survives (several!) "Build
> clean"s.
>
> Michael
--
Matt Chapman
AJDT Development, http://www.eclipse.org/ajdt
|
|
|
Powered by
FUDForum. Page generated in 0.06221 seconds
Home