ALM2 implementaion
Posted Mon, 08/02/2010 - 09:20 by itai
(4 votes)
Start to use ALM2 framework(Created by Ittay Dror) for "tikalALM" and may be as opensource platform.
1. Do needed changes to make build and install of ALM2 platform easier
2. ALM2 with SVN (ViewVC), Tikal Bugzilla (3.4) and Hudson
3. Dashboard with defined reports for these 3 components
4. Create plugin for Tikal header and remove this header from Bugzilla and ViewVC
5. Components prerequisites (for example Hudson plugins)
6. Plugins for Integrations between these 3 components
7. Create "how to write plugin" documantaion
Comments
The main motivation is to "feel" the product and learn what should be more improved in order to make the work with it smoother.
The agenda is:
1. Run ALM2 with SVN (ViewVC), Tikal Bugzilla (3.4) and Hudson
2. Create Dashboard with "boxes" for these 3 components
3. Add built-in Tikal header, and replace it in components (ViewVC and Bugzilla)
4. Documentation: create "Getting Started" and "How to write plugin" documents by the end of the session.
In order to prepare to the session, here are the steps to setup a development environment:
* checkout the sources: from http://dev.tikalk.com/svn/repos/private_branches/alm_2.0
* get buildr working: the easiest is to get a pre-made distribution from http://people.apache.org/~boisvert/buildr-1.3.5-jruby-1.4.0.zip. Make sure your Java env is set up, unzip anywhere
* compile: cd to the checkout directory and:
> /bin/buildr com.tikal.alm:base:dist:assembly
or under windows
> \bin\buildr.cmd com.tikal.alm:base:dist:assembly
* run: cd base/dist/target/assembly/bin and:
./tikal_alm
or under windows
./tikal_alm.bat
* use: open a browser at localhost:8080/alm use admin:admin to login
* development env:
** create the packages composing the target platform in eclipse
> .../bin/buildr pde:target-platform 'sources=true'
** create a target platform in eclipse and point to base/osgi/platform/target
** import the projects to eclipse:
> mv .project .project.mv
import existing projects
> mv .project.mv .project
import again to get top-level project (this is optional)
* getting started: create new eclipse plugin project
* copy content of JavaConfigManifestExtras.txt into META-INF/MANIFEST.MF
* create / copy the spring integration files
* create a Config class
I am all in favor of ALM2 it seems as if a lot of effort has been put in to ALM2 and no one is using it.
I was amazed by the mixture of technologies presented by Ittay whilst developing ALM2 framework - and it seems a waist not to use it.