Home » Newcomers » Newcomers » Hidden error?
| Hidden error? [message #268425] |
Mon, 09 February 2009 09:26  |
Eclipse User |
|
|
|
I've imported a project into my workspace, but it's shown with a red
error-cross. However, when I try to look deeper in the catalogue
structure, the error does not propagate further down, so I don't know what
might be wrong?
I can still start my Eclipse-application, and it uses the error-marked
plugin project. However, if I make any changes in the files, save them and
restart the application, the changes doesn't seem to have had any effect
on it. Anyone who might have an idea of what's wrong (and how I can
correct it)?
Sincerely,
Anna
|
|
|
| Re: Hidden error? [message #268427 is a reply to message #268425] |
Mon, 09 February 2009 09:47  |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
"Anna " <tigerkatten@gmail.com> wrote in message
news:c331fd61a6afce03cdd5f46a7b6a1d0b$1@www.eclipse.org...
> I've imported a project into my workspace, but it's shown with a red
> error-cross. However, when I try to look deeper in the catalogue
> structure, the error does not propagate further down, so I don't know what
> might be wrong?
> I can still start my Eclipse-application, and it uses the error-marked
> plugin project. However, if I make any changes in the files, save them and
> restart the application, the changes doesn't seem to have had any effect
> on it. Anyone who might have an idea of what's wrong (and how I can
> correct it)?
>
> Sincerely,
> Anna
>
My guess would be a build path error. Your project has something declared
on the Build Path that cannot be resolved. Eclipse won't be able to build
any project with a build path error. The Problem view should show you the
problem if you select the project. You can also see Build Path errors on
the Properties->Build Path page.
|
|
|
| Re: Hidden error? [message #268449 is a reply to message #268427] |
Tue, 10 February 2009 13:23 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 2/9/2009 9:47 AM, Dave Wegener wrote:
> "Anna "<tigerkatten@gmail.com> wrote in message
> news:c331fd61a6afce03cdd5f46a7b6a1d0b$1@www.eclipse.org...
>> I've imported a project into my workspace, but it's shown with a red
>> error-cross. However, when I try to look deeper in the catalogue
>> structure, the error does not propagate further down, so I don't know what
>> might be wrong?
>> I can still start my Eclipse-application, and it uses the error-marked
>> plugin project. However, if I make any changes in the files, save them and
>> restart the application, the changes doesn't seem to have had any effect
>> on it. Anyone who might have an idea of what's wrong (and how I can
>> correct it)?
>>
>> Sincerely,
>> Anna
>>
> My guess would be a build path error. Your project has something declared
> on the Build Path that cannot be resolved. Eclipse won't be able to build
> any project with a build path error. The Problem view should show you the
> problem if you select the project. You can also see Build Path errors on
> the Properties->Build Path page.
I'm curious, do you NOT have the Problems view open? I can't imagine
someone working in Eclipse on a project of any real size without it...
Eric
|
|
|
| Re: Hidden error? [message #268455 is a reply to message #268449] |
Tue, 10 February 2009 15:39 |
| Eclipse User |
|
|
|
"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:gmsgmm$h5t$2@build.eclipse.org...
> I'm curious, do you NOT have the Problems view open? I can't imagine
> someone working in Eclipse on a project of any real size without it...
So, allow me to enhance your imagination :-)
I often find myself working without the Problems view, though I wish I
didn't have to. One shortcoming of Eclipse, or at least of my Eclipse
knowhow, is that there's no way to tell a Java project that I want source
indexing but I don't expect it to actually build. I often have source code
for third-party components (such as, say, ehcache) in my workspaces so that
I can view the code for types I'm referencing, and often those projects are
not buildable within Eclipse due to other dependencies or custom build
scripts. So as far as Eclipse is concerned, there are a gazillion problems
in my workspace, making it hard for me to see the ones I care about.
I imagine I could write a Problems view filter that lets me hide problems
for the projects I don't care about, but the new filter dialog is completely
inscrutable to me and serves mainly to raise my blood pressure, so sometimes
in these cases I just end up ignoring the Problems view and paying attention
to whether there are red X's on the projects I care about. Or, I guess I
could only build the subset of projects I care about, but I'm not sure that
would get along with Maven, which I have to use on some of the workspaces,
and anyway it would be a pain to specify. And finally, M2Eclipse tends to
spit out junk in the console every time there's a build, so the Problems tab
keeps disappearing anyway. Again, I could change that, but sometimes I do
want the console to come up when it gets output.
|
|
|
| Re: Hidden error? [message #268477 is a reply to message #268455] |
Wed, 11 February 2009 09:47 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 2/10/2009 3:39 PM, Walter Harley wrote:
> "Eric Rizzo"<eclipse-news@rizzoweb.com> wrote in message
> news:gmsgmm$h5t$2@build.eclipse.org...
>> I'm curious, do you NOT have the Problems view open? I can't imagine
>> someone working in Eclipse on a project of any real size without it...
>
> So, allow me to enhance your imagination :-)
>
> I often find myself working without the Problems view, though I wish I
> didn't have to. One shortcoming of Eclipse, or at least of my Eclipse
> knowhow, is that there's no way to tell a Java project that I want source
> indexing but I don't expect it to actually build. I often have source code
> for third-party components (such as, say, ehcache) in my workspaces so that
> I can view the code for types I'm referencing, and often those projects are
> not buildable within Eclipse
When I want/need to browse sources for a library I'm using (and I
frequently do), I just attach the source ZIP to the JAR. Is there a
reason that won't serve your needs? I would never bring source into my
workspace as a project unless I needed to edit (and thus build) it.
>
> I imagine I could write a Problems view filter that lets me hide problems
> for the projects I don't care about, but the new filter dialog is completely
> inscrutable to me and serves mainly to raise my blood pressure
I agree the Problems filtering UI has become pretty poor and overly
complicated. What I've found is that defining a Working Set helps a lot
and makes Problems filtering at least usable.
> in these cases I just end up ignoring the Problems view and paying attention
> to whether there are red X's on the projects I care about. Or, I guess I
> could only build the subset of projects I care about, but I'm not sure that
> would get along with Maven, which I have to use on some of the workspaces,
> and anyway it would be a pain to specify. And finally, M2Eclipse tends to
> spit out junk in the console every time there's a build, so the Problems tab
> keeps disappearing anyway. Again, I could change that, but sometimes I do
> want the console to come up when it gets output.
It might work to pin the Console that m2e is using, set it to NOT show
on output, and then create another Console view that, hopefully, other
processes will use. I'm not sure how a Console is chosen for any given
process, but this might work.
BTW, IMHO the m2eclipse plugins need a LOT of work in the area of user
experience; this is just one of their sins.
Eric
|
|
|
| Re: Hidden error? [message #268501 is a reply to message #268477] |
Wed, 11 February 2009 19:03 |
| Eclipse User |
|
|
|
"Eric Rizzo" <eclipse-news@rizzoweb.com> wrote in message
news:gmuodu$siv$1@build.eclipse.org...
> When I want/need to browse sources for a library I'm using (and I
> frequently do), I just attach the source ZIP to the JAR. Is there a reason
> that won't serve your needs? I would never bring source into my workspace
> as a project unless I needed to edit (and thus build) it.
The Maven classpath container doesn't support doing this :-(
But also, sometimes I just want to freakin' look at some code. Somebody
says, e.g., "take a look at how it's done in such-and-so project," and I
don't want to use vi.
> BTW, IMHO the m2eclipse plugins need a LOT of work in the area of user
> experience; this is just one of their sins.
Amen. Oh, amen.
|
|
|
Goto Forum:
Current Time: Tue May 06 23:00:43 EDT 2025
Powered by FUDForum. Page generated in 0.32110 seconds |
Home