Hi
The modificationReader will read back in modifications saved by the
modification writer task.
So suppose you have projects A, B and C writing their modifications with
the modificationwriter,
you could have a project D, reading these files with the modificationReader.
The result is that project D will show all these modifactions in the
dashboard for example.
The best thing is to use the modification reader in the prebuild section.
So reading back in modifications is covered, like you found out.
The modifications themselves are not exposed to tasks, so that will require
more work.
What you can do is the following :
° in the task of your project B, check the modification file of your project
A,
parse it, and do the actions needed
° read in the modifcations of project A into project B, write them back to a
known location
parse it, and do the actions needed
Option 2 is more handy if you need to read back in modifications of
different projects,
so you set up the modification reader in the prebuild section. And your
parse script,
only needs to handle 1 file : the combined modifications written to a file
I hope this helps a bit.
with kind regards
Ruben Willems
On Fri, Oct 31, 2008 at 5:23 PM, ledbutter <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> I'm intrigued about the ModificationReader and wondering whether I
> would be able to use it for a specific use in my project. I'll start
> with a little background. I'm looking to create a cc project (I'll
> refer to it as "B") that would be dependent on a different project
> ("A") that involves checking out some database schema code. "A" is
> already setup with the ModificationWriter task. What I want "B" to be
> able to do is read in these modifications and then, depending on the
> files that were modified, apply the changes to a particular database.
> My question is how are the results of ModificationReader visible to
> other tasks in the project? Is what I am proposing feasible to do?
>
> Thanks for the great tool and the informative group.
>
