[news.eclipse.tools.jdt] Re: Build Automatically not working with versio

["Greg Babcock" <greg.babcock@xxxxxxxxxxxxxxxxx>]

Sorry for the delay, but I had to get a build out, and didn't have time to 
research the problem.

I have solved the problem, it was caused by a misconfiguration of the build 
path.  The default build path was set to {project}/bin, and should have been 
set to {project}/target/classes because of maven.  The incremental compiler 
was updating the {project}/bin folder, and run was using the 
{project}/target/classes folder.  When I performed a clean, both build paths 
were updated.

GB


"Mauro Molinari" <mauro.molinari@xxxxxxxxxxxx> wrote in message 
news:geeftf$9oh$1@xxxxxxxxxxxxxxxxxxxx
> Greg Babcock ha scritto:
>> There are no build path issues.  I was using a similar configuration with 
>> Eclipse 3.3 without any problems.
>>
>> Greg
>
> This sounds strange to me, I've never had automatic build problems apart 
> from the following cases:
> - Eclipse 3.4.0 had a compiler bug (fixed in 3.4.1) that generated 
> compilation failures with full builds and not with automatic incremental 
> builds in some circumstances
> - there's a bug in TPTP 4.5.1 (that should be fixed for the upcoming 
> 4.5.2, see bug #230050) that causes XML files not to be copied in the 
> output folder because they are filtered out (but this is true for both 
> automatic build and full build)
> - when you have buildpath problems (this is true in any Eclipse 3.x 
> version), but I think this would affect full builds, too
>
> So, try to have a look at the Eclipse log (open the Problems view or look 
> at the .log file in .metadata within your workspace) to see if there are 
> any problems that may cause your symptoms.
>
> Mauro.
>