Yeah, so the deal is that the entries in the problems view ("markers"
is the generic term for those) have a flag that specifies whether or
not they are persistent. "Problems" (errors) are generally marked
persistent so they survive a restart without requiring a rebuild all
the time. Those things are stored in workspace metadata, which lives
outside of the build folder. It is possible, as a result, that you
can manage to get errors that don't clean up properly if there's a bug
somewhere else in the build process ... This seems to be exacerbated
by switching core frameworks, and I'm not exactly sure why yet. But a
"Clean..." forces a non-incremental build to run on your project,
which explicitly tries to delete all the markers from all of the files
in the project and "rebuild" them (rebuild, in this case, for a
component = revalidate) whereas deleting the build folder may only
force a partial rebuild.
ms
On Mar 21, 2008, at 5:52 PM, Art Isbell wrote:
> On Mar 21, 2008, at 11:39 AM, Mike Schrag wrote:
>> Try selecting the project and do a Project=>Clean ... on it to
>> force a rebuild and see if the errors go away?
>
>
> Thanks! That did it. Apparently Project=>Clean does more than
> what deleting the build directory does.
>
> Did I do something wrong when I imported my projects that would
> have caused this to happen in the first place?
>
> Aloha,
> Art
>
This archive was generated by hypermail 2.0.0 : Fri Mar 21 2008 - 18:01:33 EDT