Re: Eclipse source of problems?
Re: Eclipse source of problems?
- Subject: Re: Eclipse source of problems?
- From: Pascal Robert <email@hidden>
- Date: Mon, 10 Sep 2012 14:47:03 -0400
>> ...
>>
>>> One of the problematic applications I was able to start from scratch by deleting the project and its files, copying a different working one and modifying it with the classes and user interface I started developing for the former. My feeling is that Eclipse is the cause of the problems and I am starting to hate it.
>>
>> No, Eclipse is not the cause of these problems.
>>
>>
>> Chuck
>
> I can assure you that creating a new workspace and copying the projects to it sometimes solved the problems I was having. If this is not a workspace problem I do not know what could cause it. Maybe my environment, my Java installation, other extensions or something in the system is causing the problems. I am seriously considering buying a HD to do a clean install of Mountain Lion and dedicate it to Eclipse development.
Like Chuck said, it's not a "Eclipse" problem. It might be a class path problem, a configuration problem, or other reason, but don't re-install everything! From experience of helping people with Eclipse, most of the time, re-installing everything is creating more problems than it solves.
The first thing you should do is to compare the class path of your working project with the class path of the non-working class paths. You can do it with the diff command-line tool, like this:
diff project1/.classpath project2/.classpath
Since you're using MySQL, make sure to use the plugin coming from Project Wonder, and that in the class path, MySQLPlugIn is higher than the WO frameworks (Java*.framework).
If that doesn't solve the issues, compare the Properties file of each project.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden