Message-ID: <1190217069.3813.1369400906638.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3812_262261359.1369400906638" ------=_Part_3812_262261359.1369400906638 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
JDK 5+ : Make sure that you do not use code =
constructs that require JDK 6 or higher.
Ant 1.7.1<= /p>
htt= ps://svn.codehaus.org/activiti (see http:/= /xircles.codehaus.org/projects/activiti/repo for more links including a= nonynmous access for non-committers).
After an distribution i= s unzipped (or directly in the distro/target/activiti-version dire= ctory), a number of scripts are offered to our users as well. Those scripts= can be found in=C2=A0[activiti.home]/setup/build.xml and can opti= onally use settings from [user.home]/.activiti/build.properties
As an example, here's the content of my [user.home]/.activiti/build= .properties:
activiti.home, is used in the setup/build.x= ml. It will work straight from the sources. So you can add the setup from t= he sources to your ant view in your IDE.
downloads.dir, is used in the setup/build.xml. It allows you to configure a custom loc= ation for your directory to download/find tomcat. If you don't specify this= , the default is relative to the setup directory (../downloads). So if you = use the setup/build from the sources, you might end up downloading tomcat i= nto your sources. If that still would happen, don't check it in!
tom= cat.enable.debug is used in setup/build.xml when Tomcat is install= ed. If the property is specified (whatever value), the parameter 'jpda' wil= l be added to the start commands in Tomcat's 'startup.sh' and 'startup.bat'= scripts. That will cause the remote debugging service to listen on port 80= 00.
skip.deploy.activiti.modeler=3Dtrue set this pro=
perty if the Activiti Modeler fetching from net and deployment must be skip=
Unless before a release or explicitly working on the Activiti Modeler, it's advised to set this prop= erty since sometimes a version matching the current trunk version isn't upl= oaded yet, causing the demo setup to fail.
mvn.executable=3Dmvn.bat o= n windows you have to set this property to make the calls from the ant buil= d scripts (distro/build.xml and qa/build.xml) to maven work.
= activiti.modeler.download.url: To work with Activiti Modeler or Ac= tiviti Cycle on trunk, set the property activiti.modeler.download.url= em>=C2=A0in your [user.home]/.activiti/build.properties to, e.g., = http://activiti.org/downloads/activi= ti-modeler-5.0.beta1.war if you want to use a previous release or somet= hing like file:///home/falko/sv= n/activiti-modeler/dist/activiti-modeler.war if you want to use an own build of the Activiti Modeler.
linux.browser=3Decho: Set this poperty to echo to prevent= the browser from being opened. You also use a different browser than Firef= ox through this property.
[user.home]/.activiti/tomcat-users.= xml To enable the automatic redeployment targets in qa/build.x= ml, put a tomcat-users.xml in your [user.home]/.activiti<= /em> directory with the following content:
=C2=A0= =C2=A0<?xml version=3D"1.0" encoding=3D"utf-8"?>=C2=A0 =C2=A0=C2=A0<tomcat-users>=C2=A0 =C2=A0=C2=A0 =C2=A0<role rolename=3D"manager"/>=C2=A0 =C2=A0=C2=A0 =C2=A0<user username=3D"activiti" password=3D"activiti" rol= es=3D"manager"/>=C2=A0 =C2=A0=C2=A0</tomcat-users>=09=09
You'll need to install the Maven and Subversion (SVN) plugins.
In the "Galileo -=C2=A0<= /span>[http://download.eclipse.org/releases/= galileo|http://download.eclipse.org/releases/galileo]" upda= te site, which should be available automatically, install "Collaborati= on --> Subversibe SVN Team provider". After rebooting and adding an= SVN repository, you'll be asked automatically to install one of the polari= on connectors for SVN. Just take the latest version of the polarion connect= ors. In case that doesn't happen automatically install a polarion connector= manually from "Subversive SVN Connectors Site=C2=A0[http://community.pol= arion.com/projects/subversive/download/eclipse/2.0/update-site/|= http://community.polarion.com/projects/subversive/download/eclipse/2.0/upda= te-site/]"
Install the Maven =
= First check out the activiti root from SVN as one project. Then import exis= ting projects and navigate to the modules directory. All the module project= s should then be found and can be imported in one go.
In order to hav= e BPMN code completion and validation, import BPMN's XML Schemas from a= ctiviti-engine/src/main/resources/org/activiti/impl/bpmn/parser into t= he Eclipse XML Catalog, which can be found in Preferences --> XML -->= XMLCatalog.
As much as possible try to group all related changes into si= ngle commits.=C2=A0
Before committing, run the following check to see= if all is OK.
In the commit message, start with the jira issue, a space an= d then the commit text like in this example
ACT-826 = Fixed all problems in the world=09=09
to run the test suite on spring configuration only or
mvn -Pch= eck,checkspring clean install=09=09
to combine running the en= gine testsuite on an Activiti config as well as on a Spring config= p>
If you run the checkspring profile,= the spring module will copy the engine tests over to the spring module bef= ore compiling and running the tests. =C2=A0Those tests are deleted in the '= package' build phase
If you= need to debug spring configuration test cases, just execute a=C2=A0=
in the activiti-spring mo= dule, then refresh your IDE and the classes and spring configuration will b= e in your activiti-spring project ready to be debugged.
In some situations, it might be practical to check in while some tests = are still failing. =C2=A0In that situation, make sure that the tests are ex= cluded in the modules pom.xml and that you have created a JIRA issue for it= . =C2=A0Reference the jira issue from the pom next to the excluded test. = =C2=A0And reference to the pom in the jira issue.
Build file qa/build.xml contains a number of targets for = driving the QA. It also contains convenience targets for developers to do i= ntegration testing.
More about the QA and CI infrastructure can be fo= und here:=C2=A0QA and CI Guide=
To run smoke tests on webapps, the quickest way to get s=
tarted is using the target test.demo.setup in qa/build.xml
Use target build.javadocs in qa/build.x= ml
http://www.= vitorrodrigues.com/blog/2009/07/10/debugging-ant-tasks-in-eclipse/<= h2 id=3D"DevelopersGuide-GITpointers">GIT pointers
We decided n= ot to use GIT for now. =C2=A0These pointers are here for future reference w= hen we would evaluate GIT again.
Currently there is a GIT repository fork from SVN, for experimental p= urposes. If you prefer to use GIT let Tom know and we can take that into ac= count when deciding whether to stick with it.
To use GIT as a committer you will probably want to use = ssh to authenticate automatically. Codehaus requires DSA tokens (not RSA) s= o you may need to create those first:
Ensure that your=C2=A0
~/.ssh=C2=A0directory is only readable by you (
=C2=A0should do it). You will also probably ne=
chmod 700 ~/.ssh
~/.ssh/config=C2=A0that contains these line=
Typical initial setup:
There are plenty of onlin=
e resources for git. A good one is=C2=A0[Pro Git|http=
://progit.org/book]. IntelliJ has good IDE support. Eclipse has some very a=
ctive development in=C2=A0[
span style=3D"color: rgb(0,0,0);">or=C2=A0
Mac only) very useful for visualization (launch with=C2=A0
--all=C2=A0for best results).
As a rule with GIT you do not make changes directly to remote branc= hes, but rather you create your own local branch and merge changes from the= re to the remote branch (via a local mirror).=C2=A0 Typical workflow=
Keep doing that until you=
are happy. If you want to tidy up your commits and send them as a batch in=
stead of individual changes look at=C2=A0
git rebase -i .... Now you are ready to share your work. If you want to stay on a branc=
h and collaborate with someone, push up your branch
To checkout someone else'= s remote branch for collaboration:
When you are ready to mer= ge with the remote master (dev trunk):
There are many combinatio= ns of commands that achieve the same end result as that last sequence. Your= preferred workflow might be different, and of course any time there are co= nflicts it will have to change (GIT is quite good at telling you what it th= inks is wrong in a conflict).------=_Part_3812_262261359.1369400906638--