Nick Boldt wrote:
So, again, why not store it back in the source database? Isn't fixing
the source better than copying it into a new place and maintaining
that copy. (Then repeating the process a year later.)
Because it's not a single database and is nowhere near as cohesive as
you might think
deficiencies). Fundamentally, the only difference is that you can edit
the log from within Eclipse and you have to explicitly store it somewhere.
So, again, why not store it back in the source database? Isn't fixing
the source better than copying it into a new place and maintaining that
copy.
The new IP Log Tool concept gathers information from the Foundation
database for both initial population of the log and maintenance. It
allows for far more customization than the current Automated IP Log tool
which was found to be insufficient for many of the projects that
participated in the G
Gabe and I have started work on a next generation version of the
Automated IP Log tool [1]. The new version is intended to ship as an
Eclipse plug-in.
With the new version running inside the Eclipse workbench, the developer
can decide where to store the log file: either somewhere on the project
