| Building project does not produce any .class files [message #56867] |
Mon, 25 April 2005 13:39  |
Eclipse User |
|
|
|
Originally posted by: tim.tim.tim
Hi all,
I've been using Eclipse for a while and this problem keeps popping up
its head every now and again.
Somehow source files in a project seem to get ignored when I ask Eclipse
to compile my project. I usually leave "Build Automatically" on but I've
also tried with it off also.
It seems to occur when I move source files from package to package or
when I manually delete the class files myself to force re-compilation.
The source files are on the build path (I've removed and re-added them
several times). I've tried switching between the auto and manual compile
options, cleaning the project, "Build All". Non of it seems to make a
difference.
Has anyone experienced anything similar?
Tim
p.s. This problem might of been dealt with before but I can't seem to
find a way to search the newsgroup's archives. Is there a way to do this
(as in so I don't have to download all the archived to my news reader
to perform the search!)?
|
|
|
| Re: Building project does not produce any .class files [message #57323 is a reply to message #56867] |
Tue, 26 April 2005 00:07  |
| Eclipse User |
|
|
|
Originally posted by: eclipse.rizzoweb.com
Tim Wilkins wrote:
> Hi all,
>
> I've been using Eclipse for a while and this problem keeps popping up
> its head every now and again.
>
> Somehow source files in a project seem to get ignored when I ask Eclipse
> to compile my project. I usually leave "Build Automatically" on but I've
> also tried with it off also.
>
> It seems to occur when I move source files from package to package or
> when I manually delete the class files myself to force re-compilation.
>
> The source files are on the build path (I've removed and re-added them
> several times). I've tried switching between the auto and manual compile
> options, cleaning the project, "Build All". Non of it seems to make a
> difference.
>
> Has anyone experienced anything similar?
First of all, you don't have to delete .class files manually in order to
trigger a re-compilation. You can select a Project and choose Clean...
from the pop-up menu or the Project menu bar.
As to why you can't seem to get your project to build, it is almost
always because of a problem with the Project's build path (eg, it can't
find a library JAR you specified or something like that). Right-click
the Project, choose Properties and then check the Java Build Path
section (all tabs) to see if any errors are reported in the dialog. Such
problems should also show up in the Tasks or Problems views, but may not
be obvious to you if you have lots of other entries in those views.
> p.s. This problem might of been dealt with before but I can't seem to
> find a way to search the newsgroup's archives. Is there a way to do this
> (as in so I don't have to download all the archived to my news reader
> to perform the search!)?
There's a web interface for searching the newsgroups (and other parts of
eclipse.org) - go to the Eclipse home page and look at the side
navigation panel for the Search link.
HTH,
Eric
--------
Don't make me come down there!
-God
|
|
|
| Re: Building project does not produce any .class files [message #58032 is a reply to message #57323] |
Wed, 27 April 2005 08:07 |
| Eclipse User |
|
|
|
Originally posted by: tim.tim.tim
Thanks for your advice Eric,
You were right about it being a problem on the build path. My project
had a build reference to another project which itself referenced back to
my project. The only clue to this was the little tiny 'x' icon next to
the project's root node in the 'Package Explorer' tree which when
selected put a message into the 'Problems' view.
I suppose thats fair enough, would of been nice if Eclipse had popped up
an alert box on compilation though to inform me that it had failed to
re-compile the code. Spent a long time just figuring out that it wasn't
compiling at all!
Thanks for your help once again Eric.
Tim
Eric Rizzo wrote:
> Tim Wilkins wrote:
>
>> Hi all,
>>
>> I've been using Eclipse for a while and this problem keeps popping up
>> its head every now and again.
>>
>> Somehow source files in a project seem to get ignored when I ask
>> Eclipse to compile my project. I usually leave "Build Automatically"
>> on but I've also tried with it off also.
>>
>> It seems to occur when I move source files from package to package or
>> when I manually delete the class files myself to force re-compilation.
>>
>> The source files are on the build path (I've removed and re-added
>> them several times). I've tried switching between the auto and manual
>> compile options, cleaning the project, "Build All". Non of it seems to
>> make a difference.
>>
>> Has anyone experienced anything similar?
>
>
> First of all, you don't have to delete .class files manually in order to
> trigger a re-compilation. You can select a Project and choose Clean...
> from the pop-up menu or the Project menu bar.
>
> As to why you can't seem to get your project to build, it is almost
> always because of a problem with the Project's build path (eg, it can't
> find a library JAR you specified or something like that). Right-click
> the Project, choose Properties and then check the Java Build Path
> section (all tabs) to see if any errors are reported in the dialog. Such
> problems should also show up in the Tasks or Problems views, but may not
> be obvious to you if you have lots of other entries in those views.
>
>
>> p.s. This problem might of been dealt with before but I can't seem to
>> find a way to search the newsgroup's archives. Is there a way to do
>> this (as in so I don't have to download all the archived to my news
>> reader to perform the search!)?
>
>
> There's a web interface for searching the newsgroups (and other parts of
> eclipse.org) - go to the Eclipse home page and look at the side
> navigation panel for the Search link.
>
> HTH,
> Eric
> --------
> Don't make me come down there!
> -God
|
|
|
| Re: Building project does not produce any .class files [message #58666 is a reply to message #58032] |
Wed, 27 April 2005 23:49 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.rizzoweb.com
Tim Wilkins wrote:
> Thanks for your advice Eric,
>
> You were right about it being a problem on the build path. My project
> had a build reference to another project which itself referenced back to
> my project. The only clue to this was the little tiny 'x' icon next to
> the project's root node in the 'Package Explorer' tree which when
> selected put a message into the 'Problems' view.
That sounds like your Problems view has a filter enabled on it (show
only problems of selected Project, or something like that). To set (or
remove) the filter for Problems, there is a button on the view's title
bar (not the window title bar) that looks like 3 arrows pointing right.
Click it and see if you have any such filter. If you remove any filters,
you should see the circular Projects problem show up even if that
project isn't selected.
HTH,
Eric
--------
A man talking sense to himself is no more insane than a man talking
nonsense not to himself.
-Rosencrantz & Guildenstern
|
|
|
Powered by
FUDForum. Page generated in 0.09799 seconds
] 
Search
Help
Register
Login
Home
