|
| Re: Atomizing Resource Delta [message #382237 is a reply to message #382235] |
Mon, 19 January 2009 22:44   |
|
Hi Mikhail,
I'm not sure what you're after here. What do you mean by ResourceDelta
in the context of a materialization?
If you want to materialize B only then you can issue a query for B. If
you want A without B, then you can issue a query for A and specify an
advisor node for B where you ask it to be skipped. But somehow, I doubt
that's what you want.
Can you describe a bit more about what it is you want to accomplish?
Regards,
Thomas Hallgren
Mikhail Kadan wrote:
> Hello.
>
> Let's assume we have two projects: A and B, and project A is dependent
> on B. When I materialize them in my workspace using Buckminster, I
> recieve one ResourceDelta, which contains both A and B. And I want to
> recieve two deltas, first B's (because it has no dependencies), then A's
> (as it is dependent on B). Is this possible some way?
>
> Thanks.
>
|
|
|
| Re: Atomizing Resource Delta [message #382238 is a reply to message #382237] |
Mon, 19 January 2009 23:12 |
 Mikhail Kadan
Messages: 61
Registered: July 2009 |
Member |
|
|
Hello.
Eclipse has IResourceChangeListener interface, which recieves workspace
resource modification deltas. F.e. if I delete workspace file, I'll get
delta, where this file will be marked as deleted. If I create lot's of
files at the same time (f.e. import operation), I'll recieve delta, where
all this files will be marked as created. So we can say that resource
delta is batch workspace modification, which is signalled to all who
listens to it (= implements IResourceChangeListener).
Now back to my question. I have projects A and B, A is dependant on B.
When I use Buckminster query to import them to my workspace (they are in
svn in my case), it wraps this operation in one batch, so I'll recieve
delta with combined A's and B's files. But I want to recieve first B's
delta (cause it has no dependencies), and then A's delta (as it is
dependent on B). In my case need this differentiation due to some indexing
issues. Is it possible to split workspace modifications (deltas) made by
Buckminster to correspond to dependency tree, with each project having
it's own delta?
Thanks.
|
|
|
| Re: Atomizing Resource Delta [message #382239 is a reply to message #382238] |
Mon, 19 January 2009 23:42 |
|
Hi Mikhail,
No, I'm sorry. That's not possible. We actually went through quite some
pain to make the materialization atomic in respect to change events
since we didn't want to trigger the Eclipse builder until it was
complete. I'd rather not change that since it opens up another can of worms.
Regards,
Thomas Hallgren
Mikhail Kadan wrote:
> Hello.
>
> Eclipse has IResourceChangeListener interface, which recieves workspace
> resource modification deltas. F.e. if I delete workspace file, I'll get
> delta, where this file will be marked as deleted. If I create lot's of
> files at the same time (f.e. import operation), I'll recieve delta,
> where all this files will be marked as created. So we can say that
> resource delta is batch workspace modification, which is signalled to
> all who listens to it (= implements IResourceChangeListener).
>
> Now back to my question. I have projects A and B, A is dependant on B.
> When I use Buckminster query to import them to my workspace (they are in
> svn in my case), it wraps this operation in one batch, so I'll recieve
> delta with combined A's and B's files. But I want to recieve first B's
> delta (cause it has no dependencies), and then A's delta (as it is
> dependent on B). In my case need this differentiation due to some
> indexing issues. Is it possible to split workspace modifications
> (deltas) made by Buckminster to correspond to dependency tree, with each
> project having it's own delta?
>
> Thanks.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03168 seconds
] 
Search
Help
Register
Login
Home
