As for the configuration: the Ant version is quite old; I would prefer 1.8.2.
Angelo On Apr 28, 2011, at 2:35 PM, Bram de Kruijff wrote: > He Angelo > > On Thu, Apr 28, 2011 at 11:12 AM, Angelo van der Sijpt > <[email protected]> wrote: >> What I did not mention yet is that we also have a functional offline build: >> just run the build/build.xml . We could set up a Bamboo project for that, so >> we can see the results? Who can help me with that? > > I just created a plan that is currently failing (@see > http://bamboo.amdatu.org/bamboo/browse/AMDATUSANDBOX-BNDBUILD) What > should the builder configuration be exactly? Right now I have: > > Builder Ant 1.6.5 > Build File build\build.xml > Target clean test > Build JDK JDK 1.6.0_18 > Test Results Directory **/test-reports/*.xml > > grz > Bram > > >> Angelo >> >> On Apr 27, 2011, at 11:12 PM, Angelo van der Sijpt wrote: >> >>> Hi list, >>> >>> As discussed offline quite some time ago, I added a bndtools based Amdatu >>> build to my sandbox [1]. For some more information on bndtools, see [2]. >>> You can check out the code, import the projects into Eclipse, and, for >>> instance >>> - run Amdatu by going to the 'targets' project, right-click on >>> amdatu.bndrun, and choose 'Run as -> OSGi run' >>> - try to run the integration tests by going to the 'integration tests' >>> project, right-click on bnd.bnd, and choose 'Run as -> JUnit OSGi' >>> >>> This build is based on Amdatu 0.1.0, but we have made quite some changes. >>> To name the most visible ones, >>> - We redid the gadget management mechanism: you register a service for each >>> category, and for each gadget. We do have an Extender, which allows you to >>> add arbitrary gadgets based on configuration. >>> - We added authorization for the gadget store: you need to be logged in, >>> since we can filter the gadgets you can 'see' based on your roles. >>> - We repackage Shindig but didn't put time in rewriting that to bndtools. >>> Also, built shindig for both an http, and an https environment. The shindig >>> bundle now lives in cnf/repo, since it is not built by bndtools. >>> - Moved the json apis to their own bundle >>> - We built monitoring extensions (monitor, shows the status of an Amdatu >>> instance) >>> - We built a monitoring system to watch a VM. >>> - We built a tag editor extension for Apache ACE, which probably needs to >>> be moved there. >>> - We added a 'security' bundle, which allows you to filter endpoints for >>> users. >>> - Added a bundle backup mechanism. >>> - We use metatype configurations both for provisioning, and for running >>> locally; we have an interpreter for that, but it currently does not support >>> factory configurations. >>> - We have applied an Apache License 2.0 to all artifacts. >>> >>> >>> Apart from the regular bndtools build tooling, we have added ant-based >>> tooling for running on the build server; this can be found in the 'build' >>> project. >>> >>> So, go ahead, and play around with it! We feel that bndtools is a great fit >>> for an OSGi-intensive project like Amdatu, and would like to keep using >>> that for all of Amdatu. >>> >>> Angelo >>> >>> >>> [1] https://subversion.amdatu.org/svn/amdatu/sandbox/angelos/bndtools_build >>> [2] http://www.amdatu.org/confluence/display/~marrs/BndTools >> >> >> _______________________________________________ >> Amdatu-developers mailing list >> [email protected] >> http://lists.amdatu.org/mailman/listinfo/amdatu-developers >> > _______________________________________________ > Amdatu-developers mailing list > [email protected] > http://lists.amdatu.org/mailman/listinfo/amdatu-developers _______________________________________________ Amdatu-developers mailing list [email protected] http://lists.amdatu.org/mailman/listinfo/amdatu-developers
