Home » Newcomers » Newcomers » Problems view warning and errors not listed
| Problems view warning and errors not listed [message #182903] |
Mon, 04 December 2006 15:47  |
Eclipse User |
|
|
|
Hi,
Regardless of whether I am in the Debug perspective or Java Browsing
perspective or a Java Package perspective the Problems view shows no
errors, warnings, or information even though I get warning indicators in
the edit window of my source code. How do I get these warnings and
other errors listed in the Problems view?
I removed all filters and so I don't think I'm filtering anything out now.
Thanks,
John
|
|
| | |
| Re: Problems view warning and errors not listed [message #182956 is a reply to message #182933] |
Tue, 05 December 2006 02:11  |
| Eclipse User |
|
|
|
Originally posted by: wharley.bea.com
"John" <jling@bioinformatics.ubc.ca> wrote in message
news:4574C150.3030103@bioinformatics.ubc.ca...
> I've tried doing the full save and build steps but nothing shows up under
> the Problems view still. Is there some step I'm missing? Is there any
> configuration which ties the Problems view with the rest of the IDE?
If you're still not seeing anything after a build, but there are errors
shown in the editor, there would seem to be a couple of possibilities.
1. Some sort of error is preventing the build from succeeding. Check the
error log, with View -> PDE Runtime -> Error Log (or just look in the .log
file in the .metadata directory) to see if there are any errors. It's
possible that some third-party plug-in has installed a builder that is not
working, for instance.
2. You have some sort of filter in place. You said you cleared them all, so
I'm not sure why that would be.
Do you still get this problem if you start with a fresh workspace, create a
new Java project, and create a new Java class within it, intentionally
containing an error?
Do you have any third-party plug-ins installed? What build of Eclipse are
you using, what platform are you running on?
|
|
|
| Re: Problems view warning and errors not listed [message #183062 is a reply to message #182956] |
Tue, 05 December 2006 14:39 |
| Eclipse User |
|
|
|
I've never installed any third-party plug-ins. I am running on version
3.2.1 Build M20060921-0945 on Windows XP. Now I enabled automatic
updates and I do see a problem whereby the update called "Eclipse
Project SDK 3.2.1.r321_v20060801-tQ1w49KnTArT0FZ" tries to install and
goes through the motion and then every restart of Eclipse it tries to
install the update again as if it wasn't updated before.
The PDE Runtime error logs show errors in the org.eclipse.update.core
and the org.eclipse.debug.core. With the latter error, I do notice that
even though I had previously defined an external tool Ant build
configuration, I can't recall the one that I had already defined (the
list is empty). Yet when I try to define a new one with the same name
it says a configuration with that name exists already. So it's like
it's there but Eclipse doesn't show it to me for me to use.
I did build a new workspace with a very simple class inside and if I
intentionally create an error or warning condition in there, it does
work and it does show up in the Problems view. So I don't know what is
going on with the original workspace I've got my project in.
With org.eclipse.update.core the error is:
"eclipse.buildId=M20060921-0945
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
Error
Tue Dec 05 10:53:04 PST 2006
Digest could not be parsed:Unable to retrieve remote reference
"http://download.eclipse.org/updates/3.2/digest.zip". [Server returned
HTTP response code: "404 Not Found" for URL:
http://download.eclipse.org/updates/3.2/digest.zip.]"
With org.eclipse.debug.core the error is:
"eclipse.buildId=M20060921-0945
java.version=1.5.0_09
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86
Error
Mon Dec 04 14:55:56 PST 2006
Launch configuration New_configuration at C:\Documents and
Settings\jling\workspace2\.metadata\.plugins\org.eclipse.deb ug.core\.launches\New_configuration.launch
does not exist."
Walter Harley wrote:
> "John" <jling@bioinformatics.ubc.ca> wrote in message
> news:4574C150.3030103@bioinformatics.ubc.ca...
>> I've tried doing the full save and build steps but nothing shows up under
>> the Problems view still. Is there some step I'm missing? Is there any
>> configuration which ties the Problems view with the rest of the IDE?
>
> If you're still not seeing anything after a build, but there are errors
> shown in the editor, there would seem to be a couple of possibilities.
>
> 1. Some sort of error is preventing the build from succeeding. Check the
> error log, with View -> PDE Runtime -> Error Log (or just look in the .log
> file in the .metadata directory) to see if there are any errors. It's
> possible that some third-party plug-in has installed a builder that is not
> working, for instance.
>
> 2. You have some sort of filter in place. You said you cleared them all, so
> I'm not sure why that would be.
>
> Do you still get this problem if you start with a fresh workspace, create a
> new Java project, and create a new Java class within it, intentionally
> containing an error?
>
> Do you have any third-party plug-ins installed? What build of Eclipse are
> you using, what platform are you running on?
>
>
|
|
| | |
| Re: Problems view warning and errors not listed [message #183234 is a reply to message #183178] |
Wed, 06 December 2006 09:58 |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
John wrote:
> However, I don't think documentation on how to work with CVS is very
> strong. It's not obvious what sequence of steps one should take to get
> it to correctly set up the Java project when you are dealing with CVS.
> From the wizard it seems as though you should be able to start with a
> CVS checkout right off the bat to create a new Java project. Is this a
> missing feature or a bug? Or am I missing another step? Whatever the
> case, I think something should be done to make such a common step more
> intuitive.
It's a subtle thing, and you're not the first person to have missed it.
When you are in the CVS Repository perspective and select a module to
check out, there are two choices, "Check Out" and "Check Out As..." The
first one, that you obviously chose, checks out to a plain (non-Java)
project. This is a reasonable behavior, since Eclipse is not only a Java
tool and it has no way of knowing that what you are checking out is Java.
If you choose Check Out As... then it will prompt you for the type of
project to create (or an existing project to use). At that point you
have the opportunity to make it a Java Project.
Also note that if there is a .project file in the CVS repository,
Eclipse will respect it. So once you have your project set up correctly,
checking in the .project and .classpath files is highly recommended.
As I said, you are not the first person to miss that option. There are
some Bugzilla reports about it, but I think the issue is coming up with
a UI that does not tie the CVS client to Java.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=23777
Hope this helps,
Eric
|
|
|
| Re: Problems view warning and errors not listed [message #183300 is a reply to message #183234] |
Wed, 06 December 2006 18:36 |
| Eclipse User |
|
|
|
Thanks for the pointers Eric. I'll add my suggestions to the bug
record. The Check Out As step is what I was looking for. But that part
of the workflow still needs improvement. Basically, Check Out As should
be a default (offered) step in my opinion. The problem is that when you
are asked what modules to checkout from the CVS, most people would enter
in the module name and then press ENTER. But it's the Finish button and
not the Next button that is in focus at that point. So Eclipse goes
ahead and does the checkout and ends it there, and users will think that
was the last step and they wouldn't have even seen the option to Check
Out As or the subsequent Project Wizard. The Finish button should never
be in focus by default until it's reached the last possible
configuration page. A simple UI change like this will save hours of
frustration for new users and lessen the stigma that Eclipse is
difficult to configure.
Cheers,
John
Eric Rizzo wrote:
> John wrote:
>> However, I don't think documentation on how to work with CVS is very
>> strong. It's not obvious what sequence of steps one should take to
>> get it to correctly set up the Java project when you are dealing with
>> CVS. From the wizard it seems as though you should be able to start
>> with a CVS checkout right off the bat to create a new Java project.
>> Is this a missing feature or a bug? Or am I missing another step?
>> Whatever the case, I think something should be done to make such a
>> common step more intuitive.
>
> It's a subtle thing, and you're not the first person to have missed it.
> When you are in the CVS Repository perspective and select a module to
> check out, there are two choices, "Check Out" and "Check Out As..." The
> first one, that you obviously chose, checks out to a plain (non-Java)
> project. This is a reasonable behavior, since Eclipse is not only a Java
> tool and it has no way of knowing that what you are checking out is Java.
> If you choose Check Out As... then it will prompt you for the type of
> project to create (or an existing project to use). At that point you
> have the opportunity to make it a Java Project.
>
> Also note that if there is a .project file in the CVS repository,
> Eclipse will respect it. So once you have your project set up correctly,
> checking in the .project and .classpath files is highly recommended.
>
> As I said, you are not the first person to miss that option. There are
> some Bugzilla reports about it, but I think the issue is coming up with
> a UI that does not tie the CVS client to Java.
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=23777
>
> Hope this helps,
> Eric
|
|
|
| Re: Problems view warning and errors not listed [message #266087 is a reply to message #183234] |
Wed, 05 November 2008 11:04 |
| Eclipse User |
|
|
|
Originally posted by: REMOVEdanielTHISPART.fgm.com
Eric Rizzo wrote:
....
>
> It's a subtle thing, and you're not the first person to have missed it.
> When you are in the CVS Repository perspective and select a module to
> check out, there are two choices, "Check Out" and "Check Out As..." The
> first one, that you obviously chose, checks out to a plain (non-Java)
> project. This is a reasonable behavior, since Eclipse is not only a Java
> tool and it has no way of knowing that what you are checking out is Java.
> If you choose Check Out As... then it will prompt you for the type of
> project to create (or an existing project to use). At that point you
> have the opportunity to make it a Java Project.
What's the net result of those steps? That, what can I check in my .project
file (etc.) to see if I'm set up correctly (and modify to get set up correctly,
without having to "re-install" my project).
I'm have a similar problem:
Errors do not show up in the Problem viewer, even though warnings do (or seem
to; I'm not sure they're refreshing as I first thought). I've had auto-build
turned on; I refreshed several times; I exited and re-started Eclipse (I think);
I checked and double-checked the Problems viewer's Configure Contents settings.
Finally, I tried "Build All," and my errors showed up in the problem list.
Why does Eclipse apparently not automatically re-build when Auto-build is turned
on? Why doesn't Eclipsse update the Problems list?
Is it a performance issue? Since changing a declaration in one place can cause
errors (e.g., "unknown method") in far-away places, I could imagine that Eclipse
doesn't try to keep the errors list updated because it would take a while to
re-build enough to be sure to compile all possible "far-away places" and
discover the errors (or errors' going away).
> As I said, you are not the first person to miss that option. There are
> some Bugzilla reports about it, but I think the issue is coming up with
> a UI that does not tie the CVS client to Java.
Separately, how about a change to the Problems viewer user interface?:
If the problem list is out of date because probject files have been changed but
the project hasn't been completely re-build yet, how about having a warning in
the Problems list to that effect and informing the user that re-building
will update the list (or at least hinting to that effect)? That might save
others the couple hours it took me to figure out the problem.
Daniel
|
|
|
| Re: Problems view warning and errors not listed [message #266096 is a reply to message #266087] |
Wed, 05 November 2008 15:54 |
| Eclipse User |
|
|
|
Originally posted by: eclipse-news.rizzoweb.com
On 11/5/2008 11:04 AM, Daniel B. wrote:
> Eric Rizzo wrote:
> ...
>>
>> It's a subtle thing, and you're not the first person to have missed it.
>> When you are in the CVS Repository perspective and select a module to
>> check out, there are two choices, "Check Out" and "Check Out As..."
>> The first one, that you obviously chose, checks out to a plain
>> (non-Java) project. This is a reasonable behavior, since Eclipse is
>> not only a Java tool and it has no way of knowing that what you are
>> checking out is Java.
>> If you choose Check Out As... then it will prompt you for the type of
>> project to create (or an existing project to use). At that point you
>> have the opportunity to make it a Java Project.
>
> What's the net result of those steps? That, what can I check in my .project
> file (etc.) to see if I'm set up correctly (and modify to get set up
> correctly,
> without having to "re-install" my project).
>
>
> I'm have a similar problem:
>
> Errors do not show up in the Problem viewer, even though warnings do (or
> seem
> to; I'm not sure they're refreshing as I first thought). I've had
> auto-build
> turned on; I refreshed several times; I exited and re-started Eclipse (I
> think);
> I checked and double-checked the Problems viewer's Configure Contents
> settings.
>
> Finally, I tried "Build All," and my errors showed up in the problem list.
>
> Why does Eclipse apparently not automatically re-build when Auto-build
> is turned
> on? Why doesn't Eclipsse update the Problems list?
If you have Build Automatically enabled, then Build All wouldn't be
enabled. When Build Automatically is enabled, the Problems view *is*
kept up-to-date; everything is built whenever a source file is saved or
touched.
BTW, that has nothing to do with my comments that are quoted above; I
think that discussion ended up being related to the fact that the user
had checked out a project from CVS but not made it a Java project. In
your case, since you can build the project and get error markers, it is
obviously a Java project.
Eric
|
|
|
| Re: Problems view warning and errors not listed [message #266103 is a reply to message #266087] |
Wed, 05 November 2008 17:52 |
| Eclipse User |
|
|
|
Originally posted by: REMOVEdanielTHISPART.fgm.com
I wrote:
> I'm have a similar problem:
>
> Errors do not show up in the Problem viewer, even though warnings do (or seem
> to; I'm not sure they're refreshing as I first thought). I've had auto-build
> turned on; I refreshed several times; I exited and re-started Eclipse (I think);
> I checked and double-checked the Problems viewer's Configure Contents settings.
>
> Finally, I tried "Build All," and my errors showed up in the problem list.
> Why does Eclipse apparently not automatically re-build when Auto-build is turned
> on? Why doesn't [Eclipse] update the Problems list?
Never mind. Auto-build actually wasn't still on.
Daniel
|
|
|
Goto Forum:
Current Time: Sat Jul 26 01:03:10 EDT 2025
Powered by FUDForum. Page generated in 0.10885 seconds |
Home