Re: [Dltk-dev] Re: Getting a wrong/older version of a ModuleDeclaration

[赵忠伟 <zhaozhongwei@xxxxxxxxxxxxxxxx>]

project->clean will trigger the full build.

And for some reason we(pdt) use  org.eclipse.php.internal.core.builder.ParserBuildParticipantFactory instead of org.eclipse.dltk.core.builder.ParserBuildParticipantFactory.And if you want to trigger FULL_BUILD every time you save a file,I think you can create your own ParserBuildParticipantFactory.

On Tue, Aug 17, 2010 at 9:54 PM, Gabriel Petrovay <gabipetrovay@xxxxxxxxx> wrote:

Hi,

Researching more into the problem I found that our IBuildParticipant
receives now other build types in the IBuildContext. Before it was
receiving FULL_BUILD when saving a file. Now it receives
INCREMENTAL_BUILD instead. This was our problem with the non-updating
cache.

But now when is a full build is triggered?

Thanks!

Gabriel

On Tue, Aug 17, 2010 at 3:10 PM, Gabriel Petrovay
<gabipetrovay@xxxxxxxxx> wrote:
> Hi
>
> I am using SourceParserUtil.getModuleDeclaration(ISourceModule) to
> retrieve a ModuleDeclaration. What I get is an older version of my
> module's declaration. Probably a cached one.
>
> This happens when I modify a ISourceModule and save it. When I want to
> access it through SourceParserUtil.getModuleDeclaration() I get the
> older version before the file was edited/saved.
>
> Shouldn't the saving of a document update the ISourceModule on the AST
> cache? Or how can I control this or make sure I get the latest saved
> version of my modules?
>
> This seems to be a regression for us since we migrated to DLTK 2.0
>
>
> Thanks!
>
> --
> MSc Gabriel Petrovay
> Mobile: +41(0)787978034
> www.28msec.com
>



--
MSc Gabriel Petrovay
Mobile: +41(0)787978034
www.28msec.com
_______________________________________________
dltk-dev mailing list
dltk-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dltk-dev

-- 

Thanks!

Best Regards!

Zhao