Hi Bryan, What is this proposed zip for? As I understand it, users could use our jars 2 ways:
1) runtime dependencies on Beehive libraries from a Beehive app (all jars in a web app classloaded or a system classloader explicitly) 2) buildtime dependencies (referring to something like netui-compiler.jar at build, but not including it in the app) But both are use cases only for Beehive applications. What is wrong with requiring a Beehive distribution for both cases? -Mike > > 4.1 Beehive Libraries > > Beehive libraries would consist of just jars of Beehive code and nothing > else. This distribution would be for users who have no intention of > developing with Beehive--they just need it as a dependency. Also, it > would benefit packagers who want to re-distribute Beehive with other > software. This would be shipped in a file like apache-beehive-lib-[VERSION].zip It would have all the contents under lib/ in the current distribution as well as the NOTICE and LICENSE files.
