I have little experience in Java/Groovy/Grails, about 1 year using Eclipse and some weeks using GGTS, and I always got my projects with build path problems, or other related problems, with apparently no reason. The environment seems to be buggy. Any tip?
Below there's an screenshot of a project I was working on and, after a computer restart, a lot of wild build path problems had appeared.
PS.: To solve these problems I closed the project in GGTS, used a grails clean in console, opened the project again (all the problems still were there), then I just gave a look into properties > Java Build Path and all problems have gone. These steps makes no sense for me.
Like others I would not recommend Eclipse. All variants(sts,ggts,vanilla eclipse+plugins) are unstable at least on Juno, IMHO.
I personally use emacs, but like #James, I would suggest IntelliJ:
stable as in no strange internal errors pop up while doing Grails coding, no project corruptions.
better completion, especially dynamic methods
Related
I've been using Eclipse IDE for... nearly a month now and one day all my projects had suddenly an error sign over them. I've already tried to assign in the Library tab from Build Path the JDK I already have (the jdk.11.0.2, or at least that's the one it recognizes) and it still popped up 30 error messages. Mainly these two: The project cannot be built until build path errors are resolved and The project was not built due to "release 15 is not found in the system". Fix the problem, then try refreshing this project and building it since it may be inconsistent.
I'm using the latest version of Eclipse IDE.
I've tried to clean it, it didn't work. I've tried to search on Stack Overflow but I found answers I didn't understand. I've downloaded a JDK package from here (https://jdk.java.net/15/), the Windows version if it matters, but I realized I do not actually know how to actually install it. If someone would be so kind to guide me a little I would be grateful. Thank you for considering my question.
I had this problem with an auto update.
Had to go to my project properties and change the JDK Compliance level.
First a little background. I can go from netbeans 8.0 to 12 and open an existing older project that was built with netbeans native builder (pretty sure it's ant), do a clean and build, and the project runs perfect with zero problems. You can totally be unaware of build.
Now the problem, gradle. I did my first gradle project, all was good, ran fine. Then a few days later netbeans informed me there was an update to gradle, I updated, restarted the ide, and nothing. The project would not build anymore, etc.
How, and I plea for help here, how do you make it so you can update gradle, and just press on with a clean and build?
Meaning, I want to be unaware that gradle even exist, I should not have to spend time fixing a build tool, I should be able to update, and forget I’m even using it. Any help is appreciated.
Been using netbeans for years, and never encountered such a mess.
Also if it's not possible in netbeans, I'll use eclipse, but I'd like to not even think about the build tool just like in the past. Any hints, tips?
Or after an update to gradle, is there some little thing that needs to be done?
I have used native build for years, mostly netbeans and some in eclipse and never needed to read one word of the ant documentation, it just always works.
I'd like to make Gradle use Eclipse project dependencies. Unlike this question, I don't want to do any export as I don't want to hunt down problems due to forgetting to re-export after a change. And unlike this question, I don't want to integrate Gradle into Eclipse at all, as I'm satisfied with how my Eclipse works (it's much faster than a Gradle build) and I'm also afraid that my Eclipse 3.7.2 may be too old for such games.
Ideally, I'd like something like
dependencies {
compile allFilesFromEclipse()
}
Actually, getting the JARs would suffice.
What I've tried: Just some light googling. I could imagine parsing the .classpath file myself, but it's not done in 5 minutes, so I'm asking if there's an existing solution.
I am afraid you won't find much help. It is not obvious what problem you want to solve here. Most developers prefer to base their build on a build tools rather than expect that they will replicated an IDE setup everywhere.
As for Eclipse 3.7.2: I am not sure why you want to stick with that but gradle eclipse generates files that work with this version.
I have recently had a problem with Eclipse. I am developing a java application. It suddenly freezes whenever I try to save a file. Indeed, it happens to some files in my project while it works fine with the others. I have checked the .log file in my workspace and there is no error message! I tried to disconnect my project from GIT, but the problem persisted. It drives me crazy. I have to restart Eclipse many times everyday.
Any solution would be greatly appreciated.
Such kind of issues should provide all related info: OS, Java, Eclipse version, list of plugins installed. Example of file saved. CPU, RAM size, memory setting for Eclipse.
Without knowing those details some recommendation would be to analyze and try to find the cause by comparing:
try on other PC,
with other Java version
other Eclipse version
the same Eclipse version without any additional plugins.
increase Eclipse memory settings
Check if it is build related by disabling automatic build.
Check if there are "Save Action" configured in Preferences.
and so on.
maybe some plugin causes that, but usually people just go with new Eclipse instance instead of comparing different plugins combinations.
See also How can you speed up Eclipse?
Eventually, it's worked. I created a new workspace and import it my project to it. Everything works well since then, like a magic! It seems the problem occurred because my workspace was too old. I have been working on the same workspace since more than 2 years.
Thanks fellows for your time to help.
I am noticing a strange issue with Eclipse Indigo. It is Building Workspace again and again even though there is no change in the code!
In Progress bar it prints
Building Workspace 44%
..
Building Workspace 10%
..
Building Workspace 33%
Any idea what is going on here? For the time being I have unchecked the 'Build Automatically' flag.
I have tried the following trick couple of times and this seems to work more often than not:
Uncheck Build Automatically flag
Refresh all the projects in the workspace
Re-enable the automatic build after sometime by checking the Build Automatically flag
Note that as I mentioned earlier this is a trick and not a resolution. But, hope others facing these issues will find this helpful.
Yes, I have noticed that too and it can be rather annoying. I have reverted to manual compiling in Eclipse by switching auto-building off (under project).
Compiling manually is a bit old-school, but it works for me. I prefer to compile, package and test the code at the command line using maven.
(I'll probably get a downvote for this approach (i.e. not using integrated tools, etc.), but it works for me and it works well! At least I'm not using VIM for coding Java! :))
If you are using Windows 7, then the Windows indexing in some directories can cause automatic rebuilds in Eclipse: see Bug 342931 - Windows 7 Libraries trigger rebuilds.