Add Git (Gitorious) to Tikal ALM using ALM2 platform
The plan for the session:
- add a new tab for Gitorious
- add plugin for Bugzilla-Gitorious integration, in Bugzilla it should "override" viewvc parameters and link
- hudson Git plugin - configure with Gitorious in order to see nicer change log
- git hooks: add check bug id to pre-commit and pre-receive hooks for central repo
- add Gitorious installation/configuration to Tikal ALM suite
* We will work in pairs like on the previous session.
* All participants should be ready with alm2 dev environment.
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/
- get buildr working: the easiest is to get a pre-made distribution from http://people.apache.org/~
- compile: cd to the checkout directory and:
> /bin/buildr com.tikal.alm:base:dist:
or under windows
> \bin\buildr.cmd com.tikal.alm:base:dist:
- 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
Please don't forget to register! :)
Comments
Hi,
I am trying to follow the instructions and wrote a script to automate the process, however the build fails during some internal buildr phase related to maven repos.
Here is the script:
And this is the error (I understand its related to maven but i do not wish to start and change the repos used by buildr, or should I ?):
and later this:
The message about Cucumber is harmless
The longer error starts with:
Failed to download org.apache.xml:com.springsource.org.apache.xml.resolver:jar:1.2.0, tried the following repositories:So it can't find the artifact in question in any of the listed repositories. Try to locate it and either add another repository to buildfile or update the version of the artifact to a newer version that does exist. Try to first look at spring's enterprise repository
Thanks man,
I used a "wired" network connection (instead of wireless) and the artifacts are now downloading however I get:
lopi@freebsd:~/Downloads$ ./install.sh Starting Tikal ALMListening for transport dt_socket at address: 8000 Debug options: file:/home/lopi/Downloads/tikalk/alm_2.0/base/dist/target/assembly/.options not found osgi> * lopi@freebsd:~/Downloads$ Time to load bundles: 575 !SESSION 2011-01-06 11:03:49.161 ----------------------------------------------- eclipse.buildId=unknown java.version=1.6.0_22 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -install /home/lopi/Downloads/tikalk/alm_2.0/base/dist/target/assembly Command-line arguments: -console -consoleLog -debug -install /home/lopi/Downloads/tikalk/alm_2.0/base/dist/target/assembly -data /home/lopi/Downloads/tikalk/alm_2.0/base/dist/target/assembly/var -configuration /home/lopi/Downloads/tikalk/alm_2.0/base/dist/target/assembly/etc/equinox !ENTRY com.tikal.alm.web.core 4 0 2011-01-06 11:03:50.518 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.dappit.Dapper.parser; version="0.3.0" at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321) !ENTRY com.dappit.dapper.MozillaParser 4 0 2011-01-06 11:03:50.523 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: No match found for native code: external:lib/linux/i386/libMozillaParser.so; processor=x86; osname=linux, external:lib/windows/MozillaParser.dll; processor=x86; osname=winxp, external:lib/macosx/libMozillaParser.jnilib; processor=x86; osname=�macos x� at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321) !ENTRY com.tikal.alm.plugins.dashboard 4 0 2011-01-06 11:03:52.321 !MESSAGE !STACK 0 org.osgi.framework.BundleException: The bundle could not be resolved. Reason: Missing Constraint: Import-Package: com.tikal.alm.web.core; version="0.0.0" at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:305) at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355) at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074) at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616) at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508) at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299) at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321) !ENTRY com.tikal.alm.plugins.wikify 4 0 2011-01-06 11:03:52.323The relevant error is:
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: No match foundfornative code: external:lib/linux/i386/libMozillaParser.so; processor=x86; osname=linux, external:lib/windows/MozillaParser.dll; processor=x86; osname=winxp, external:lib/macosx/libMozillaParser.jnilib; processor=x86; osname=�macos x�In the bundle manifest there are directives pointing to native libraries based on os attributes. Your OS is not there (what is it?). Lior had something similar with his OS, I don't remember the resolution, but he has an updated bundle. Ask if he can upload it.Now that you mention it I did remember he said something about 32 and 64 bit. This is my machine:
> uname -a
Linux freebsd 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010 x86_64 GNU/Linux