iThoughts » Eclipse http://www.ithoughts.de Upgrade your Brain Thu, 12 Jan 2012 16:51:23 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 We need a “Delete old Documentation Day” http://www.ithoughts.de/we-need-a-delete-old-documentation-day http://www.ithoughts.de/we-need-a-delete-old-documentation-day#comments Sat, 12 Feb 2011 07:22:51 +0000 Akku http://www.ithoughts.de/?p=588
DODD - Delete Old Documentation Day 15 feb
Old documentation in maven and ServiceMix caused much trouble for me, and I know for many other people. And I’m sure these are not the only projects that have a lot of meaningless, deprecated documentation around doing nothing than confusing people. Then people always cheat and say they are to busy to update documentation everytime they add a new feature or they fix a bug or something else changes; as documentation is nothing more than time waste, right?

You know, we have Google. If all the wrong documentation were gone, we would either find the correct documentation or the programmers would realize nobody can use their software and had to write new, up-to-date documentation.

Therefore, I propose DODD! Let’s make a Let’s make a “Delete Old Documentation Day”, once a year, where everyone just deletes old stuff that is misleading or inaccurate to make the whole average documentation clear and concise?

What do you think? How about 15.02.? The day after Valentine’s we should have enough love for everyone else and the outdated documentation they need to read.

Related Posts:

flattr this!

]]> http://www.ithoughts.de/we-need-a-delete-old-documentation-day/feed 0 " Maven + Eclipse Maven Plugin Issue NoRepositoryConnectorException http://www.ithoughts.de/maven-eclipse-maven-plugin-issue-norepositoryconnectorexception http://www.ithoughts.de/maven-eclipse-maven-plugin-issue-norepositoryconnectorexception#comments Fri, 21 Jan 2011 14:31:20 +0000 Akku http://www.ithoughts.de/?p=555 Should you use Eclipse and Maven and the Maven plugin for Eclipse, you maybe came around this exception. An update of the Eclipse plugin brought me this problem.

Just to tell you the quick fix of this problem: goto “Windows –> Preferences –> Maven –> Installations”, and if you see there’s an Embedded Snapshot used after the last update of the plugin, click “Add…” and browse to the path of your local maven2 installation that you used before.

Related Posts:

flattr this!

]]> http://www.ithoughts.de/maven-eclipse-maven-plugin-issue-norepositoryconnectorexception/feed 0 " Eclipse “Out of Memory Error” and “GC overhead limit exceeded” http://www.ithoughts.de/eclipse-out-of-memory-error-and-gc-overhead-limit-exceeded http://www.ithoughts.de/eclipse-out-of-memory-error-and-gc-overhead-limit-exceeded#comments Tue, 12 Oct 2010 16:00:05 +0000 Akku http://www.ithoughts.de/?p=454
Syntax Error - Folded Up Beyond All Recognition
If you happen to have Eclipse not responding anymore sometimes, the reason could be that you sit on a 64bit machine where eclipse needs more memory. Be sure to have (at least) the following configurations in your eclipse.ini (I even use bigger values for the PermSizes):

-Xms512m
-Xmx1024m
-XX:PermSize=64m
-XX:MaxPermSize=128m
Creative Commons License photo credit: Simon Pow

Related Posts:

flattr this!

]]> http://www.ithoughts.de/eclipse-out-of-memory-error-and-gc-overhead-limit-exceeded/feed 11 " Eclipse Initializing Java Tooling Error on 64bit Windows 7 http://www.ithoughts.de/eclipse-initializing-java-tooling-error-on-64bit-windows-7 http://www.ithoughts.de/eclipse-initializing-java-tooling-error-on-64bit-windows-7#comments Thu, 19 Nov 2009 20:09:22 +0000 Akku http://www.ithoughts.de/?p=162 Just a short note about an error I resolved lately.

Eclipse Initializing Java Tooling hangs at 1% while eclipse uses a lot of resources while configuring org.eclipse.jst.j2ee.internal.web.container … I’m on Windows 7, 64bit, 64bit JDK, running as non-admin.

This error seems to have some connection to the installed plugins, or with the last exit of eclipse. I found a forum entry “on the internets” where one user said he just deleted the lock file in his workspace’s metadata folder. This didn’t work for me. Another user mentioned that you can delete or rename the folder to resolve the issue:

WORKSPACE_HOME/.metadata/.plugins/org.eclipse.core.resources/.projects

This worked for me, eclipse starts back on error-free again – BUT when closing eclipse, another error appears, that says that metadata in this folder could not be saved (something to do with the servers). Starting back up again after this gives me the same error again, Java Tooling hanging at 1%

Switching the workspace seems to help. Saying that, the workspace is corrupt somehow.So the single working workaround is deleting the .metadata folder for your eclipse workspace and start that workspace anew, importing projects, generating a new server. Can’t reproduce the error now, but I still guess that its something one of the plugins save wrongly in the project-metadata. I suspect its the JavaScript support, the springide-plugin or the subclipse plugin, as these are the plugins that a guy from this forum-thread had installed that I also use.

Well, never mind. Its a bunch of plugins in one giant IDE-framework. Can’t work on a 64bit Win7, right?

Related Posts:

flattr this!

]]> http://www.ithoughts.de/eclipse-initializing-java-tooling-error-on-64bit-windows-7/feed 12 "