|
|
Re: Disable Dependecy Path Update [message #517351 is a reply to message #516126] |
Sat, 27 February 2010 03:51 |
Don Park Messages: 6 Registered: July 2009 |
Junior Member |
|
|
In one I have around 10 projects. In another, about 20. Behavior is same for both.
Nothing really noticeable except sporadic build failures and WTP related errors.
Re build, it appears that projects are not building in proper order despite having both Maven dependencies and Eclipse dependencies to determine proper build-order. Build failures are always class not found which indicate maven dependency path update either failed or there is some sort of race condition between IAM builder and Java builder. Cleaning or rebuilding failed projects will remove all the errors.
Re WTP related errors, I am hoping new Eclipse 3.5SR2 update will fix them. If not, only suspect remaining is IAM's Webtools support since my Eclipse env is stock J2EE Eclipse dist + IAM.
Update: Forgot to add that WTP related errors are usually preceded by "Initializing Java Tooling" failure on startup.
[Updated on: Sat, 27 February 2010 04:32] Report message to a moderator
|
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04067 seconds