Buildship produces internal error with separate output folders and composite builds

buildship

(Kenzie Togami) #1

I’m not sure if this is a bug in Buildship or a misconfiguration on my end, but when I have a composite build that includes another Eclipse project, I get the following error from Buildship upon refresh:

Java Model Exception: Java Model Status [Cannot nest output folder '<project name>/bin/main' inside output folder '<project name>/bin']
	at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:786)
	at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3227)
	at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3189)
	at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:3201)
	at org.eclipse.jdt.internal.core.JavaProject.setOutputLocation(JavaProject.java:3148)
	at org.eclipse.buildship.core.workspace.internal.OutputLocationUpdater.update(OutputLocationUpdater.java:31)
	... (additional lines excluded for brevity)

I’m running Buildship 2.2.0.v20171211-1404.


(Jaywalkable) #2

I am facing the same issue.


(Stefan Oehme) #3

Can you please provide a small example project reproducing the issue?


(Tuan Anh) #4

I delete .project file then everything work fine.


(Sølve) #5

If that doesn’t work, delete: all of the eclipse files/foldes within project , e.g., .settings, .classpath, .project… Delete project from eclipse(without files), re-import; worked for me.