Apex Code Development You need to sign in to do that
Don't have an account?
chris_centra odd behavior in Force.com IDE?
hello -
i've been using the force.com ide for many years to write apex/vf/etc. just in the past couple of days, i'm seeing very odd behavior. normally, when i save code that contains a compile-time error, the Problems tab shows a red symbol and tell me what the error is. suddenly, when there's an error, i get a warning that the code could only be saved locally and not to sfdc (technically true, but it doesn't tell me my error...if i remove the errant code or fix the error, it saves without incident). another example - equally strange, normally when test coverage code fails, again there's a red icon in the Apex Test Runner tab and i can drill down to the specific error. now it doesn't do that. it only shows that there are warnings, and i have to review the Debug Log to see if there is an issue and what the specific issue is.
i had been using v27 when this started occurring, so i updated to v28, but the behavior is the same. this is really bizarre to me because for its shortcomings, the eclipse tool has been solid as a rock since i started using it. anyone have an idea of what's going on?
thanks for your time.
chris
i've been using the force.com ide for many years to write apex/vf/etc. just in the past couple of days, i'm seeing very odd behavior. normally, when i save code that contains a compile-time error, the Problems tab shows a red symbol and tell me what the error is. suddenly, when there's an error, i get a warning that the code could only be saved locally and not to sfdc (technically true, but it doesn't tell me my error...if i remove the errant code or fix the error, it saves without incident). another example - equally strange, normally when test coverage code fails, again there's a red icon in the Apex Test Runner tab and i can drill down to the specific error. now it doesn't do that. it only shows that there are warnings, and i have to review the Debug Log to see if there is an issue and what the specific issue is.
i had been using v27 when this started occurring, so i updated to v28, but the behavior is the same. this is really bizarre to me because for its shortcomings, the eclipse tool has been solid as a rock since i started using it. anyone have an idea of what's going on?
thanks for your time.
chris
thanks
chris