“Job found still running after platform shutdown eclipse” Problem with my Eclipse Juno

English: Total Solar eclipse 1999 in France. *...

(Photo credit: Wikipedia)

Hi, it is some times that I don’t write new articles on my blog, this time I would like to report how I solved this problem on my running Eclipse workspace.

First of all I have deleted (as I have read in the past in many other sites ) the .snap files inside the org.eclipse.core.resources folder with a command like:

rm YOUR_WORKSPACE_FOLDER/.metadata/.plugins/org.eclipse.core.resources/.snap

but for me this has not been sufficient, so trying with every folder inside the .plugins I discovered that I simply need to delete (or rename) the folder org.eclipse.e4.workbench:

rm -rf YOUR_WORKSPACE_FOLDER/.metadata/.plugins/org.eclipse.e4.workbench

Starting again Eclipse this time worked and now I can again use it with all my previous configuration.
I have not googled to know what is the purpose of the data inside the org.eclipse.e4.workbench and also I have to say that of course I have tested only on my Eclipse Juno instance

Have a nice day

Advertisements

Eclipse & SVN on Linux : How to add files to ignore list automatically

Eclipse (software)

Eclipse (software) (Photo credit: Wikipedia)

First of all you need to create a new file on the root of the project with the list of file to ignore like the following (this is a typical list of file that we need to exclude from an Eclipse project)

target
target/**
bin
bin/**
.classpath
.project
.settings

and after on the console (shell) you have to run the following command assuming that you have called the previous file ignore.txt

svn propset svn:ignore -RF ignore.txt .

(Please note the “.” at the end of the command). The -R is the recursive option

Now you can run eclipse and access to the SVN View and commit all the local changes

This is very usefull if you have alread a large project that you want to import on Eclipse and do you want to avoid to ignore every file manually by means of eclipse

Eclipse Access Restriction Error

Clickide 3

Image via Wikipedia

When in Eclipse you have an error like: “Access restriction: The constructor AppletAudioClip(URL) is not accessible due to restriction on required library C:\Programmi\Java\jdk1.6.0_24\jre\lib\rt.jar” You simply need to follow these steps to avoid compilation error:

Click on the Properties of your project Go to Java Compiler–>Errors/Warnings search for “Deprecated and Restricted API” and set to warning “Forbidden reference (access rules)” item.

That’s it.

Enable keywords substitution using Eclipse and Subversion (SVN)

Vista-eclipse

Image via Wikipedia

To enable keywords substitution as I usually have with the CVS, you just need to enable a svn properties on the Eclipse project configuration.

These are the steps to activate the svn-keyword-substitution feature in Eclipse:

  1. Install Subclipse into your Eclipse application
  2. Right-mouse-click on your project folder, and choose Team => Set Property from the popup menu (note to click on the root of the project folder)
  3. Enter the property name:  svn:keywords
  4. Enter the text property:  Author Date Id Revision HeadURL
  5. Click the  Set property recursively checkbox
  6. OK

Note that on large project files this action could take also several minutes. Now keywords are substituted when you commit a file in SVN, just like they were by using CVS.  Also, you can shorten Revision to Rev and HeadURL to URL.

So if you now have a file like:

// File name: $HeadURL$
// Revision: $Revison$
// Last modified: $Date$
// Last modified by: $Author$
//
//  file description

commiting it to the SVN will result into:

//  File name: afile.php
//  Revision: 1
//  Last modified: 2010-11-4 14:53
//  Last modified by: quonn
//
//  file description