I deleted the release folder which was generated by eclipse (CDT) when I first built my project; but now when I try rebuilding the sources, eclipse does not regenerate the complete release folder along with the make files. Rather, it reports the following error:
Errors occurred during the build.
Errors running builder 'CDT Builder' on project '<project name>'.
Resource '/<project name>/Release/objects.mk' does not exist.
Resource '/<project name>/Release/objects.mk' does not exist.
I'm using eclipse neon2 with cdt. I tried searching for a solution online, but I couldn't find any. How do I solve this problem and regenerate the release file?
I tried refreshing the project, by right clicking the project in the project explorer and then clicking refresh before building the project. The project now builds without any problems and the release folder got regenerated.
It would have been nice if Eclipse did that automatically.
Related
I have cloned my Liferay 7.1 workspace from my Github repository. When I try to get Assistance in Liferay IDE using Control+Space, I get error:
This compilation unit is not on the build path of a java project
This happens on the new module project created in the same workspace(that was cloned from Github).
But when I create/import module from my local workspace that was created by Liferay for first time, this issue is not there.
I feel like there is some extra workspace setting that I am not doing in my Github workspace. Like we had to create build.username.properties in the SDK folder for Liferay 6.2. Totally stuck and no solutions anywhere.
I tried fixing Project Build path and Project Facets but did not help.
The way you did it in your own answer obviously solved it. My take on this is: The problem was most likely the .project file, because it contains all the configuration that eclipse requires, and the error message you post is an indicator that eclipse doesn't know what to do with these files.
The .project file can be regenerated from gradle settings, typically by choosing "gradle / refresh" (from memory, from the context menu of the project/workspace in Project Explorer), which will read the gradle settings and apply them to the eclipse world. This might happen automatically, but it might also need some manual push - next time you might want to try this, because just copying random files rarely is a good idea. You might end up pointing to other directories far outside of your workspace, and wonder why a local change is not picked up.
There were some differences between the workspace that I imported from Github and the one that Liferay was creating on my local. I opened both the workspaces in Beyond Compare. Following are the files that had major differences. I made them same and it started working after Gradle Refresh in Eclipse.
liferay-workspace/gradle/wrapper/gradle-wrapper.properties
liferay-workspace/.project
liferay-workspace/gradle.properties
liferay-workspace/gradlew
liferay-workspace/settings.gradle
I was trying to clone a project in Eclipse and after copying it into the same directory, I got a lot of build path errors, even after deleting the copy of the project. So, I decided to back up the original project, delete it from the directory and try importing it again. However, when I try to import it I get a "Gradle build daemon disappeared unexpectedly" error. I have looked extensively on this and other sites and found no solution, I tried deleting the .gradle folder as well as several others, to no avail. Can someone please help me?
It didn't fix the problem, but I managed to find a workaround by creating a new LibGDX project with the same name and then copying the 'src' folders from each subproject into their respective folders in the new project. Their were still a few problems with the android version, but once I picked an android target and added 'gen' to the source folders in the build path, it worked.
I have been using Eclipse Luna and sprint boot for quite a while. Just today, when I created a new project I am getting the following build error,
Build path contains duplicate entry: 'org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8' for project 'TomcatHttpDemo'
I am not sure if this is related to this problem but I tried
properties> Java Build Path > Libraries
and found that 'JRE System Library[JavaSE-1.8] was listed twice. I deleted one of them and then cleaned and re-built the project. I got a bunch of new errors. These errors were all related to deleting the JRE system library. I even restarted Eclipse several times to clear out any lingering errors.
I was running Luna 4.4 and upgraded to Mars 4.5 but the problem continues to persist. I can build my old projects with no problems at all. Using Luna or Mars the old projects build and execute properly. Any time I try to create a new project I get the duplicate entry error. Any help would be appreciated.
if i understand your problem it's library issue with your project so
1.Select your project then go to Properties
2.Java build Path
3.in the Top select Libraires
4.add a JRE System Library
5.check the Execution Environment Then Click to Environments
6.On the left click to Installed JREs
7.Then Click To add , Standard VM
8.click To directory Then go to /yourprograms/java/jdk 1.8
9.then Click finish after this check what you just added and click ok
10.when everything is closed update your maven Project
i hope it helps you
I am using eclipse luno (4.4) in the linux environment.
When I sharing project with svn repository in eclipse, it gives this error.
"Sharing failed. ... is already a working copy for a different URL; perform update to complete it"
I added normal java project to that svn repository successfully. But when I add another project (a java web project) it gives this error.
May be this is because I have tried to add this project so many times. But I deleted those directories with "svn delete [URL]" command and they were successfully deleted.
Can anyone tell me how to fix it?
The error occur at the last step in eclipse sharing project dialog.
how can I update it? svn update is not working
Following steps will help you
-Remove .svn directory from your project
-refresh your project on eclipse
-share project to svn
I have a gradle project I had imported into eclipse (it is the libgdx sample project "The Plane that couldn't fly good" here), and it runs fine.
Now I exited eclipse, moved the project directory elsewere, re-launched eclipse, and it complains it can not find the project files (fine, I moved them in other directory).
So I am trying to open the project from the new directory but I am unable to find a file to feed eclipse with (such as a .sln file for visual studio); I tried to re-import the project, but eclipse complains:
trunk.theplanethatcouldntflygood-android existing workspace project
theplanethatcouldntflygood-android has the same name
So I am wondering if I am trying an impossible use case (NEVER change a gradle project directory) or I am missing something?
Delete the old project in Eclipse first and then import it again.