branch merging
Borislav Iordanov
I think you can merge your 'distributed hypergraph' branch into the
main branch now. The code in the 'peer' sub-package is quite
autonomous (nothing in the other packages depends on it) so it can be
compiled in a separate jar. I think that it should be optional in the
build. So I suggest modifying the ant script as follows:
1) Keep the creation of the hgcore jar 'hypergraphdb.jar' as it is. It
should still not contain anything from the peer code and it should
only have BerkeleyDB as its sole external dependency.
2) Add a target 'peer' that creates a 'hgpeer.jar' that contains only
the code under the 'peer' package. This will have a dependency on
jxta.jar etc. (Btw, do you still need this beanflow stuff? If not, you
can just get rid of it...).
3) Add a target 'full' that creates a 'hgdbfull.jar' that contains
everything, including the peer package.
4) Add a target 'all' that creates all of the above jar files.
Do you want to do all that?
Cheers,
Boris
--
"Frozen brains tell no tales."
-- Buckethead