| Build Automatically not working with version 3.4.1 [message #257122] |
Thu, 30 October 2008 11:05  |
Eclipse User |
|
|
|
I created a new Eclipse 3.4.1 installation along with a new workspace. With
Build Automatically turned on, I have to do a clean in order to get the
project to build.
My installation is:
- eclipse-java-ganymede-SR1-win32.zip,
- Maven Embedder 2.1.0
- Maven Integration for Eclipse 0.9.6
- Perforce P4WSAD 2008.1
Are there any known issues that could cause this problem.
|
|
|
|
|
|
| Re: Build Automatically not working with version 3.4.1 [message #257644 is a reply to message #257133] |
Sat, 29 November 2008 16:03  |
| Eclipse User |
|
|
|
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@cardinis.com> wrote in message
news:geeftf$9oh$1@build.eclipse.org...
> 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.
>
|
|
|
Powered by
FUDForum. Page generated in 0.06461 seconds
Home