Thanks for everyone voicing their opinions on this one. Based
on all the +1s, it looks like we have an agreed upon direction
(remove logstore altogether as part of the AR1 release).
If anyone has an issue with that -- please post a -1 with
rationale soon. Thanks.
-Jim
On Aug 29, 2007, at 6:38 PM, Dan Creswell wrote:
One other question comes to mind... How should we handle the
logstore
portion of the outrigger build? Should we leave it as is,
disable it
in the build, or remove the sources completely? If we leave it
as is,
we would need to consider including the prebuilt-outrigger-
logstore.jar
in the source distribution, as Phil suggested, to allow builds
without
the need for a Jini installation. Disabling the logstore jar'ing
target, on the other hand, removes the dependency on the Jini
binary
installation but leaves the logstore sources in a unaltered state.
In all cases, logstore cannot be used without pro.zip (the PSEpro
runtime library), but persistence is still attainable through
the use
of the snaplogstore implementation.
I'd lean towards what's expedient to get out "AR1" in short order
-- but
I do think we're going to have to bite the bullet and probably
remove
logstore from the build going forward. It doesn't seem to have long
term viability.
My vote is to remove logstore altogether and do it for AR1.
+1
