| Eclipse Errors and Warnings [message #518776] |
Thu, 04 March 2010 18:19  |
Eclipse User |
|
|
|
Can anyone direct me to a good source material, either in the help menu, on the web, or otherwise, that will help me with step by step, explanatory approach to resolving the hundreds of errors and warnings the IDE generates.
The Quick Fix tool hardly fixes the tons errors generated. It offers suggestions to some of them, and even so, does not say which one of those suggestions is the answer to the particular problem. i am really stuck with tons of these errors and warnings trying to learn the IDE. Your help is highly appreciated.
dGlobal
|
|
|
| Re: Eclipse Errors and Warnings [message #518929 is a reply to message #518776] |
Fri, 05 March 2010 08:38  |
| Eclipse User |
|
|
|
Hi,
You may want to provide more detailed information on what you are trying
to do and what errors you are getting. In general, double-clicking on an
error in the problem view should open an editor positioned at the
offending line/location.
Cheers,
Steffen
On 04/03/2010 23:19, dGlobal wrote:
> Can anyone direct me to a good source material, either in the help
> menu, on the web, or otherwise, that will help me with step by step,
> explanatory approach to resolving the hundreds of errors and warnings
> the IDE generates.
>
> The Quick Fix tool hardly fixes the tons errors generated. It offers
> suggestions to some of them, and even so, does not say which one of
> those suggestions is the answer to the particular problem. i am
> really stuck with tons of these errors and warnings trying to learn
> the IDE. Your help is highly appreciated.
>
> dGlobal
>
|
|
|
|
|
| Re: Eclipse Errors and Warnings [message #519359 is a reply to message #518776] |
Mon, 08 March 2010 10:52 |
| Eclipse User |
|
|
|
Steff
As i mentioned the errors and warnings are so ridiculously numerous. They are not just one or two to remember what they are. And it makes you wonder if the IDE is of any good.
Seriously, if I had written a single code as the application built, it would've been perfectly reasonable to think that my coding was full of errors. But, if the IDE, with its ability to AUTO-GENERATE app files, generates such enormous errors and warning then, frankly, the IDE doesn't know what the hell it's doing. IT HAS A SERIOUS FLAW. In essence, it simply doesn't work right. Let's face it, Netbeans doesn't do that. Flex Framework doesn't go that; and on, and on....
The Quick Fix and Content Assist utilities should, i am told, help to fix these errors and warnings but they come back with the messages: "There no suggestions for this error/warning". The most frustrating thing is the fact that you cannot find anyone to seriously help straiten this apparent flaw up. Hope you're serious at helping.
dGlobal
|
|
|
| Re: Eclipse Errors and Warnings [message #519415 is a reply to message #519359] |
Mon, 08 March 2010 13:15 |
| Eclipse User |
|
|
|
"dGlobal" <dGlobal@nyc.rr.com> wrote in message
news:hn36g0$ti9$1@build.eclipse.org...
> Steff
>
> As i mentioned the errors and warnings are so ridiculously numerous. They
> are not just one or two to remember what they are. And it makes you wonder
> if the IDE is of any good.
> Seriously, if I had written a single code as the application built, it
> would've been perfectly reasonable to think that my coding was full of
> errors. But, if the IDE, with its ability to AUTO-GENERATE app files,
> generates such enormous errors and warning then, frankly, the IDE doesn't
> know what the hell it's doing. IT HAS A SERIOUS FLAW. In essence, it
> simply doesn't work right. Let's face it, Netbeans doesn't do that. Flex
> Framework doesn't go that; and on, and on....
>
> The Quick Fix and Content Assist utilities should, i am told, help to fix
> these errors and warnings but they come back with the messages: "There no
> suggestions for this error/warning". The most frustrating thing is the
> fact that you cannot find anyone to seriously help straiten this apparent
> flaw up. Hope you're serious at helping.
>
> dGlobal
In order for us to help you, we will need more information. Could you
provide more details about how you got to the point of so many errors in
your project. Let us know what programming language you are using. What
type of project are you working on. Is this an existing project that you
just started to use Eclipse to work on? Did the errors occur sudenly on a
project that previously was clean?
From your description, my only guess would be a missing configuration step
or a missing dependency. Some examples of the error messages you are
receiving would also give us something to go on.
An IDE can only work with what it is given. Errors/warnings that are the
result of ambiguous, mispelled, conflicting, or syntax problems can often be
provided with hints from the IDE. However, Errors/warnings that are the
result of missing information can't be easily fixed by the IDE since it
doesn't know where to look for the information.
|
|
|
|
| Re: Eclipse Errors and Warnings [message #519488 is a reply to message #519478] |
Mon, 08 March 2010 20:18 |
| Eclipse User |
|
|
|
dGlobal wrote:
> I do not know how else to explain this because i am completely new at
> Eclipse. I have just started learning it recently. Again, i was just
> trying out "Creating your first Java project" to get myself acquainted
> with working with Eclipse. I did not have to write a single code. The
> system generated all the codes. All I did was write the app a name i.e.
> "JUnit" in a name field and confirmed file location.
> The errors/warnings generate after compilation. When i tried a fix using
> Quick Fix, i get several suggestions, yes. I just don't know which ones
> of those suggestions actually fixes any particular error/warning. Here
> is an example of the errors:
>
> Constructor is a raw type. References to generic type Constructor <T>
> should be parametrized.
> Here is my problem with that. It is almost impossible to understand the
> logic behind the auto-genrated application files when the codes are
> erroneous.
>
> dGlobal
Ok, I think I can help you. It appears as though you are going through
the tutorial in the Eclipse help. The messages you are seeing are from
code generated by Eclipse. You actually imported source code that is
part of the tutorial.
The "Constructor is a raw type" message is actually a warning. It is
related to Java Generic types. Generics were added to the Java language
spec in version 5. The spec requires the warning when generic capable
classes are used without parameterizing the class. In this case, the
tutorial assumes that the compiler is set to version 1.4. That is what
the part about Use an execution environment is about. If you set the
compiler compliance to 1.4. The majority of the warnings go away.
You can do this now by Right clicking on the Junit project and selecting
Properties from the context menu. In the properties dialog, select Java
Compiler. At the top of the dialog, make sure that Enable project
specific settings are set.
Uncheck Use compliance from Execution Environment. In the Compiler
Compliance drop down, select 1.4. Save the properties. You should be
asked to perform a full build. Select yes. After the build, you will
still see some warnings (around 20). They are expected, and you can
ignore them.
Good luck
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03776 seconds
Home