Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 418574

Summary:	Failed to add classpath entry for generated source folder classes
Product:	[Eclipse Project] JDT	Reporter:	Matt Kusnierz <matthew.kusnierz>
Component:	APT	Assignee:	Generic inbox for the JDT-APT component <jdt-apt-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	eclipse, matthew.kusnierz
Version:	4.3
Target Milestone:	---
Hardware:	PC
OS:	Windows 7
Whiteboard:	stalebug

Description Matt Kusnierz

2013-10-03 05:42:40 EDT

The following error is generated in the eclipse error log when annotation processing is enabled (even though the annotation processor appears to work correctly):

Failed to add classpath entry for generated source folder classes

Exception:

Java Model Exception: Java Model Status [Source folder 'src/main/java' in project 'XXXX' cannot output to distinct source folder 'target/classes']
	at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:784)
	at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3096)
	at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3058)
	at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3111)
	at org.eclipse.jdt.apt.core.internal.generatedfile.ClasspathUtil.updateProjectClasspath(ClasspathUtil.java:208)
	at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedSourceFolderManager.addToClasspath(GeneratedSourceFolderManager.java:117)
	at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedSourceFolderManager.ensureFolderExists(GeneratedSourceFolderManager.java:192)
	at org.eclipse.jdt.apt.core.internal.generatedfile.GeneratedFileManager.compilationStarted(GeneratedFileManager.java:359)
	at org.eclipse.jdt.apt.core.internal.AptProject.compilationStarted(AptProject.java:58)
	at org.eclipse.jdt.apt.core.internal.AptCompilationParticipant.aboutToBuild(AptCompilationParticipant.java:255)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.initializeBuilder(JavaBuilder.java:590)
	at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:167)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)

Comment 1 Walter Harley

2013-10-04 01:12:56 EDT

Thanks for the report.  Clearly this does not happen for all people on all projects.  Have you been able to determine what is special about yours?  What conditions are necessary to reproduce this?

Comment 2 Eclipse Genie

2019-12-12 15:27:03 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.