Hello Dion, On Sep 27, 2011, at 11:06 AM, Dion Meijer wrote:
> when upgrading BlueConic from Amdatu 0.1.1 to version in the trunk, it proved > to be difficult to make the correct selection of bundles and configuration > files from the core and subprojects. Why? Are our descriptions of what the individual bundles do not clear enough? Tell us what we should improve. > I would like to suggest that documentation or a build target is added for > building a release containing the required bundles from the core and > subprojects to deliver a OpenSocial dashboard based on Cassandra as was > available in the 0.1.0 release (and maybe some other configurations). > This working reference stack would also help to determine if a bug is caused > by Amdatu or by software depending on it and help new Amdatu users get > started more quickly. Work is being done to come up with a "demo" that contains all Amdatu components: http://jira.amdatu.org/jira/browse/AMDATU-427 The problem with build targets for these things is that we can come up with many different variations of our stack, and trying to make targets for all of them simply won't scale. Our best bet is if we can properly explain what the individual components do, so you can decide for yourself what combination you want to use. There is no "reference stack" :) > Also, for Amdatu developers a working reference stack is required to test > deployment of bundles. The demo should get them started. Greetings, Marcel
_______________________________________________ Amdatu-users mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-users
