| unable to resolve imports after project rebuild [message #11566] |
Thu, 01 May 2003 22:23  |
Eclipse User |
|
|
|
I have a project with about 1650 source files. all is fine unless I rebuild
the project. Then I will receive about 900 errors indicating that an import
can not be resolved. If we open every file that has this error and resave
it, the errors will disappear -- until the next time the project is rebuilt.
This is using Eclipse 2.1, JDK 1.3.1, windows 2000. I checked the bug
database, but didn't find any thing relevant.
thanks much for any help.
Leon Webster
|
|
|
|
| Re: unable to resolve imports after project rebuild [message #15033 is a reply to message #14739] |
Tue, 06 May 2003 09:31  |
| Eclipse User |
|
|
|
Originally posted by: mccull1.does.not.like.spam.us.ibm.com
This kind of thing is extremely hard to report properly.
I have seen a similar problem, but like the poster we are talking about a
project with thousands of source files. Narrowing the cause is nearly
impossible, because as soon as you tweak something the problem dissapears.
I know in my case (and probably in the poster's), we're dealing with
confidential information and so are limited in our reporting options.
-Andrew
"Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
news:b97v2g$rbl$1@rogue.oti.com...
> This would be worth a new bug report, with steps to reproduce. Please log
it
> against JDT/Core, and we'll investigate.
>
> "Leon Webster" <leon@leonwebster.com> wrote in message
> news:b8skrt$v18$1@rogue.oti.com...
> > I have a project with about 1650 source files. all is fine unless I
> rebuild
> > the project. Then I will receive about 900 errors indicating that an
> import
> > can not be resolved. If we open every file that has this error and
resave
> > it, the errors will disappear -- until the next time the project is
> rebuilt.
> > This is using Eclipse 2.1, JDK 1.3.1, windows 2000. I checked the bug
> > database, but didn't find any thing relevant.
> >
> > thanks much for any help.
> >
> > Leon Webster
> >
> >
>
>
|
|
|
| Re: unable to resolve imports after project rebuild [message #16005 is a reply to message #15033] |
Tue, 06 May 2003 23:58 |
| Eclipse User |
|
|
|
I will add a bug report. But I am not sure how to reproduce the problem.
In my group there are 7 or 8 developers using eclipse and only 2 of us have
this problem.
As Andrew points out, the files are confidential, so I can't send you a
directory.
Thanks much.
Leon
"Andrew McCullough" <mccull1@does.not.like.spam.us.ibm.com> wrote in message
news:b98dd3$70g$1@rogue.oti.com...
>
> This kind of thing is extremely hard to report properly.
>
> I have seen a similar problem, but like the poster we are talking about a
> project with thousands of source files. Narrowing the cause is nearly
> impossible, because as soon as you tweak something the problem dissapears.
> I know in my case (and probably in the poster's), we're dealing with
> confidential information and so are limited in our reporting options.
>
> -Andrew
>
> "Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
> news:b97v2g$rbl$1@rogue.oti.com...
> > This would be worth a new bug report, with steps to reproduce. Please
log
> it
> > against JDT/Core, and we'll investigate.
> >
> > "Leon Webster" <leon@leonwebster.com> wrote in message
> > news:b8skrt$v18$1@rogue.oti.com...
> > > I have a project with about 1650 source files. all is fine unless I
> > rebuild
> > > the project. Then I will receive about 900 errors indicating that an
> > import
> > > can not be resolved. If we open every file that has this error and
> resave
> > > it, the errors will disappear -- until the next time the project is
> > rebuilt.
> > > This is using Eclipse 2.1, JDK 1.3.1, windows 2000. I checked the bug
> > > database, but didn't find any thing relevant.
> > >
> > > thanks much for any help.
> > >
> > > Leon Webster
> > >
> > >
> >
> >
>
>
|
|
|
| Re: unable to resolve imports after project rebuild [message #19832 is a reply to message #16005] |
Mon, 12 May 2003 07:28 |
| Eclipse User |
|
|
|
Understood. The key for solving this issue is to isolate a few steps
reproducing this problem.
We haven't seen it on our end.
"Leon Webster" <leon@leonwebster.com> wrote in message
news:b9a08s$9t6$1@rogue.oti.com...
> I will add a bug report. But I am not sure how to reproduce the problem.
> In my group there are 7 or 8 developers using eclipse and only 2 of us
have
> this problem.
>
> As Andrew points out, the files are confidential, so I can't send you a
> directory.
>
> Thanks much.
>
> Leon
> "Andrew McCullough" <mccull1@does.not.like.spam.us.ibm.com> wrote in
message
> news:b98dd3$70g$1@rogue.oti.com...
> >
> > This kind of thing is extremely hard to report properly.
> >
> > I have seen a similar problem, but like the poster we are talking about
a
> > project with thousands of source files. Narrowing the cause is nearly
> > impossible, because as soon as you tweak something the problem
dissapears.
> > I know in my case (and probably in the poster's), we're dealing with
> > confidential information and so are limited in our reporting options.
> >
> > -Andrew
> >
> > "Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
> > news:b97v2g$rbl$1@rogue.oti.com...
> > > This would be worth a new bug report, with steps to reproduce. Please
> log
> > it
> > > against JDT/Core, and we'll investigate.
> > >
> > > "Leon Webster" <leon@leonwebster.com> wrote in message
> > > news:b8skrt$v18$1@rogue.oti.com...
> > > > I have a project with about 1650 source files. all is fine unless I
> > > rebuild
> > > > the project. Then I will receive about 900 errors indicating that
an
> > > import
> > > > can not be resolved. If we open every file that has this error and
> > resave
> > > > it, the errors will disappear -- until the next time the project is
> > > rebuilt.
> > > > This is using Eclipse 2.1, JDK 1.3.1, windows 2000. I checked the
bug
> > > > database, but didn't find any thing relevant.
> > > >
> > > > thanks much for any help.
> > > >
> > > > Leon Webster
> > > >
> > > >
> > >
> > >
> >
> >
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.02925 seconds
Home