T
Torben
Guest
Hi, we have seen some issues with path name and package name casing (Same problem with 10.2B on Windows 10) When we don't use same case in package and directory name. But problem with 11.5.1 seems to have solved itself. So maybe a Microsoft bug, that has been solved in an update from MS!? This has been reported to support. !MESSAGE Errors running builder 'Progress Builder' on project 'APIREST'. !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/APIREST/.rcode/Apipro' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215) ... at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) !SUBENTRY 1 org.eclipse.core.resources 4 368 2015-10-19 18:13:36.661 !MESSAGE Resource '/APIREST/.rcode/Apipro' does not exist.
Continue reading...
Continue reading...