I like this idea:
> 2. The artifact will have a directory structure as follows: > > WebApps > - built portal code, in war file to be served off of Tomcat > - stack war file > - ideally, users can simply deploy what is in this directory to Tomcat > Lib > - sample usergrid props file > Launcher > - Jar file for launcher in separate dir > Docs > - docs describing how to get up and running w/ Usergrid > SDKs > - each SDK will be in its own subdirectory > UGC > - can’t forget our awesome command line utility > - should this include the UGC code? Or just a readme file telling how > to install (it is a Ruby Gem)? Or should we simply reference UGC in the > Docs? ... Rod's artifact (with Lewis' and any other compliance-necessary additions) in src and dist form. But we still need to publish libraries to mvn central *where feasible* (not sure what that means either). Maybe the mvn-targeted libraries are just the contents of Java contents "stack" - what we did originally back in the day? Basically, we got a big ol' heterogeneous bear of a project, so figuring out the final form of this is hard. Rod's approach gives us a single "here you go" for consistent documentation, but we need to publish artifacts to further adoption and development.
