[Dev] ZAP: Part I

[Brett Wooldridge]

The first part of the ZAP separation is complete, but there's still several build and deployment related items to sort out.  However, everything should be buildable and runnable in it's present state.

My recommendation is to just grab a fresh checkout of the 'ziptie' alias, but if you have work in progress you can just:


 1.  Update the world
 2.  Checkout all of the new org.ziptie.zap.* projects
 3.  Delete the matching (former) org.ziptie.server.* equivalents of those projects

Note, there are still some org.ziptie.server projects left, and these will say - they are application-level projects not ZAP projects.  There are a few project naming decisions remaining, for example Leo's new org.ziptie.client project ... should it be org.ziptie.zap.client?  Maybe.  It would be highly valuable to a consumer of the ZAP and is free of any ZipTie UI dependencies.

Ed, if you're listening, I need you to throw down with your build/crate changes.  I burned about 4 hours trying to stack the ZipTie build on top of the ZAP build before finally waving off.  What I'd like is for the ZipTie crate to be dependent on the ZAP create (I had dependency versioning issues).  I also haven't figured out how to simply have the ZipTie build call the ZAP build and then compile on top of that output.   Seems like the zdist task crate handling needs to be aware of crate dependencies as well (the org.ziptie.zap.crate lives in ZapBuild/crates not in Build/crates).  Leo, feel free to jump in here too.

-Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ziptie.org/pipermail/dev/attachments/20080115/f5e97b57/attachment.html