Eclipse Community Forums: Eclipse Platform » Problem using setDerived

Help

Home

Home » Eclipse Projects » Eclipse Platform » Problem using setDerived - how to clear derived mark from memory?

Show: Today's Messages :: Show Polls :: Message Navigator

Problem using setDerived - how to clear derived mark from memory? [message #515891]

Mon, 22 February 2010 06:41

Gerald Rosenberg

Messages: 106
Registered: July 2009

Senior Member

Eclipse 3.5

Programmatically generating a series of ICompilationUnit's. Save and marking as derived works
fine.

Problem occurs when trying to save a subsequent re-generation of the file: get the standard popup
asking whether to save to a derived file.

Have tried first unsetting derived without success:

cu.getCorrespondingResource().setDerived(false);
cu.save(new NullProgressMonitor(), true);
cu.getCorrespondingResource().setDerived(true);

According to the setDerived JavaDoc, the derived mark is maintained in memory. Apparently, the
setDerived(false) is not effective/flushed to disk until the project is closed or entire workspace
is saved. Closing and reopening the project is not a practical option.

So, how do I silently save a cu to a prior saved, derive-marked file?

Thanks...

Report message to a moderator

Re: Problem using setDerived - how to clear derived mark from memory? [message #516984 is a reply to message #515891]

Thu, 25 February 2010 16:52

Dani Megert

Messages: 3802
Registered: July 2009

Senior Member

Gerald Rosenberg wrote:
> Eclipse 3.5
>
> Programmatically generating a series of ICompilationUnit's. Save and marking as derived works
> fine.
>
> Problem occurs when trying to save a subsequent re-generation of the file: get the standard popup
> asking whether to save to a derived file.
>
I assume you have the file open in an editor right? If so, it might be a
bug. I suggest you file a bug against Platform Text with an example
plug-in to reproduce the issue. As a workaround you could disable the
preference (see
org.eclipse.ui.texteditor.AbstractDecoratedTextEditorPrefere nceConstants.EDITOR_WARN_IF_INPUT_DERIVED)
to warn when a derived file is changed.

HTH
Dani

> Have tried first unsetting derived without success:
>
> cu.getCorrespondingResource().setDerived(false);
> cu.save(new NullProgressMonitor(), true);
> cu.getCorrespondingResource().setDerived(true);
>
> According to the setDerived JavaDoc, the derived mark is maintained in memory. Apparently, the
> setDerived(false) is not effective/flushed to disk until the project is closed or entire workspace
> is saved. Closing and reopening the project is not a practical option.
>
> So, how do I silently save a cu to a prior saved, derive-marked file?
>
> Thanks...
>

Report message to a moderator

Re: Problem using setDerived - how to clear derived mark from memory? [message #517433 is a reply to message #516984]

Sat, 27 February 2010 22:03

Gerald Rosenberg

Messages: 106
Registered: July 2009

Senior Member

In article <hm69su$h3v$1@build.eclipse.org>, daniel_megert@ch.ibm.com
says...
>
> Gerald Rosenberg wrote:
> > Eclipse 3.5
> >
> > Programmatically generating a series of ICompilationUnit's. Save and marking as derived works
> > fine.
> >
> > Problem occurs when trying to save a subsequent re-generation of the file: get the standard popup
> > asking whether to save to a derived file.
> >
> I assume you have the file open in an editor right? If so, it might be a
> bug.

It was a bug, just not in Eclipse. Turned out that a method call
executed shortly before ".setDerived(false)" was, as a very obscure side
effect, touching the file. Bottom line, setDerived works as (I)
expected.

>
> HTH
> Dani
>

Thanks much,
Gerald

Report message to a moderator

Previous Topic:	How out of date is "Creating Eclipse Plugins" for Eclipse 3.5.2?
Next Topic:	Formatting Eclipse console output

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 24 23:58:53 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter