Skip to Content

Wiki source code of Building WOLips

Version 128.1 by Pascal Robert on 2012/02/11 08:50
Hide last authors
Pascal Robert 128.1 1 {{tip title="Not Required!"}}
2 You do not have to build WOLips to use it. It is easily available via Eclipse's Software Update functionality. The update site is: [[http:~~/~~/wocommunity.org/wolips/3.7/stable/>>url:http://wocommunity.org/wolips/3.7/stable/||shape="rect"]]
3 {{/tip}}
Pascal Robert 119.1 4
Pascal Robert 128.1 5 {{note}}
6 The following instructions about building WOLips are fine if you need to build a distribution of WOLips. However, they aren't so great if you're debugging WOLips. Instructions on how to do that are posted here [[doc:Debugging WOLips]].
7 {{/note}}
Pascal Robert 118.1 8
Pascal Robert 128.1 9 Prior to building WOLips, you will want to get your dependencies installed properly. Check out the [[doc:Installing WOLips]] page for information on the dependencies for WOLips.
Pascal Robert 118.1 10
Pascal Robert 128.1 11 (% style="color: rgb(0,0,0);" %)**Prerequisites**
Pascal Robert 118.1 12
Pascal Robert 128.1 13 ==== Install eGit or another Git client ====
Pascal Robert 118.1 14
Pascal Robert 128.1 15 See [[Getting Started With Git>>doc:WEB.Getting Started with Git]] for information on how to obtain a Git client.
Pascal Robert 118.1 16
17 ==== Install the m2eclipse plugin (Eclipse 3.5 instructions) ====
18
mark_ritchie 122.1 19 1. Help -> Install New Software
Pascal Robert 128.1 20 1. Click "Add..."
Pascal Robert 118.1 21 11. Name = M2Eclipse
Pascal Robert 128.1 22 11. Location = [[http:~~/~~/m2eclipse.sonatype.org/update/>>url:http://m2eclipse.sonatype.org/update/||shape="rect"]]
Pascal Robert 118.1 23 11. Click "OK"
24 1. Expand "Maven Integration"
25 1. Select "Maven Embedder"
26 1. Select "Maven Integration for Eclipse"
27 1. Click "Next>"
28 1. Click "Finish"
29
Mike Schrag 110.1 30 == Checking out and Building from the Commandline ==
Mike Schrag 88.1 31
Pascal Robert 128.1 32 1. Checkout the {{code language="none"}}trunk/woproject{{/code}} folder from Subversion
33 {{code language="none"}}git clone{{/code}} [[git:~~/~~/github.com/wolips/wolips.git>>url:git://github.com/wolips/wolips.git||shape="rect"]]{{code language="none"}}{{/code}} woproject
34 1. {{code language="none"}}cd woproject{{/code}}
35 1. {{code language="none"}}ant{{/code}}
36 1. The first build will fail out telling you that it couldn't find {{code language="none"}}wobuild.properties{{/code}} – That's OK
37 1. Edit {{code language="none"}}~/Library/wobuild.properties{{/code}}
38 1. Add a line: {{code language="none"}}eclipse.home=/path/to/your/eclipse{{/code}}
39 1. Call ant with the build.version argument:
40 11. {{code}}ant -Dbuild.version=3.7.SomeNumber{{/code}}If you get the error {{code language="none"}}'build.xml:73: taskdef A class needed by class org.apache.velocity.anakia.AnakiaTask cannot be found: org/jdom/JDOMException'{{/code}}, you can do one of two things. You can build with {{code language="none"}}-Dno.docs=true{{/code}} to skip the javadoc step, or (untested) you can drop {{code language="none"}}jdom-b8.jar{{/code}} from {{code language="none"}}woproject/projects/lib{{/code}} into your {{code language="none"}}ANT_HOME/lib{{/code}} folder.
41 1. The build went into {{code language="none"}}temp/dist{{/code}}
Mike Schrag 104.1 42 1. Profit
Mike Schrag 88.1 43
Mike Schrag 110.1 44 == Checking out and Building inside of Eclipse for Deployment ==
Mike Schrag 104.1 45
Pascal Robert 128.1 46 1. Add the wolips Git repository [[https:~~/~~/github.com/wolips/wolips/>>url:https://github.com/wolips/wolips/||shape="rect"]] in the Git Perspective's Repository View
47 1. Right-click (or equiv) on the {{code language="none"}}build.xml{{/code}} inside of the "woproject" project and Run As=>Ant Build ...
Pascal Robert 118.1 48 1. Switch to the Properties tab and check for the definition of eclipse.home in the Properties list
Pascal Robert 128.1 49 1. If {{code language="none"}}eclipse.home{{/code}} does not exist, uncheck "Use global properties" and then click "Add Property"
50 1. In the Add Property dialog, make the name {{code language="none"}}eclipse.home{{/code}}, click Add Variable, select {{code language="none"}}eclipse_home{{/code}} from the list, and click OK
Pascal Robert 118.1 51 1. Click Apply to save your changes
Mike Schrag 108.1 52 1. Run
Pascal Robert 128.1 53 1. Once it is complete, you may need to right-click=>refresh your project and you will have a {{code language="none"}}temp/dist{{/code}} folder with the plugin site in it.
Mike Schrag 108.1 54
Mike Schrag 110.1 55 == Checking out and Building inside of Eclipse for Development (PDE) ==
Mike Schrag 108.1 56
Pascal Robert 128.1 57 1. Add the wolips Git repository [[https:~~/~~/github.com/wolips/wolips/>>url:https://github.com/wolips/wolips/||shape="rect"]] in the Git Perspective's Repository View
58 1. You can select individual plugins you would like to work on by browsing to {{code language="none"}}trunk/woproject/wolips/{{/code}} in the Subversion repository and checking out the plugins you are interested in. To checkout complete sets of plugins, you could also use the [[doc:Eclipse Team Project Set]].
Mike Schrag 86.1 59
Pascal Robert 118.1 60 == An approach to setting up the development and test environment for WOLips Plugin. ==
Mike Schrag 100.1 61
Pascal Robert 128.1 62 In order to do WOLips Plugin development you will need two eclipse environments: Development and Test.
Mike Schrag 100.1 63
Pascal Robert 128.1 64 1. Follow the Checking out and Building inside of Eclipse for Deployment in you primary Eclipse installation (i.e. /Application/eclipse) and workspace. This will be you development environment.
65 1. the {{code language="none"}}temp/dist{{/code}} folder is your Local Site for the Test Environment.
66 1. Create a second copy of "clean" Eclipse under /Users/<me>/Developer/eclipse (this could be any where). This will be your Test Environment.
67 1. In the test environment, follow the [[doc:Installing WOLips]] instructions, using your {{code language="none"}}temp/dist{{/code}} directory as the Local Site. Install the plugins.
Pascal Robert 118.1 68 1. Use the Test environment to exercise/test the changes from your locally modified Plugin.
Mike Schrag 100.1 69
Pascal Robert 128.1 70 1. When you need to repeat the process, shut down the Test Environment, delete the org.objectstyle.* files in the features and plugins directories under the /Users/<me>/Developer/eclipse directory. Change the source code in the primary environment and build. (Each build took 3 min 37+ seconds on my Mac Book Pro 17"). Once the build is done, then reinstall the plugin in the Test Environment. The Local Site should still be selected.
Mike Schrag 100.1 71
Pascal Robert 128.1 72 == Building WOLips with Jenkins Continuous Build server ==
Mike Schrag 100.1 73
Pascal Robert 118.1 74 Hudson is a Java base continuous build server that allows you to build and test your project automatically. It can be easily configured to build WOLips in a few simple steps.
Mike Schrag 100.1 75
Pascal Robert 128.1 76 1. Install Eclipse 3.7. You need it to be able to build WOLips.
77 1. Copy the necessary plugins from your machine to the Eclipse installation on the server. In this example it has been copied to /usr/local/eclipse
78 The currently required plugins for a deployment build are
79 ~* JProfiler (Update Site: [[http:~~/~~/wocommunity.org/documents/tools/jprofiler6/>>url:http://wocommunity.org/documents/tools/jprofiler6/||shape="rect"]])
80 ~* JRebel (Update Site : [[http:~~/~~/www.zeroturnaround.com/update-site/>>url:http://www.zeroturnaround.com/update-site/||shape="rect"]])
81 1. Create a new job in Jenkins to build WOLips. You can use the [[following sample config>>url:https://github.com/wocommunity/JenkinsJobs/tree/master/WOLips||shape="rect"]] or you can add a new job with the following configuration:
82 11. Project Name: WOLips
83 11. Git Repositories: git:~/~/github.com/wolips/wolips.git
84 11. Use update: Checked
85 11. Poll SCM: 59 * * * * //(59 can be replaced with any number between 0 and 59)//
86 1. Add the following build tasks to the job {{code title="Execute Shell"}}
87 echo build.version=3.7.${BUILD_NUMBER} > build.properties
88 echo eclipse.home=/usr/local/eclipse >> build.properties
89 echo user.home=${WORKSPACE} >> build.properties
90 {{/code}} {{code title="Invoke Ant"}}
91 Targets: dist
92 {{/code}} If you want to deploy the build to a web server to serve as an update site add a task that is something like this
Pascal Robert 118.1 93
94 {{code title="Execute Shell"}}
95
Pascal Robert 128.1 96 rm -fr /usr/local/www/apache22/data/wolips/*
97 /bin/cp -prv ${WORKSPACE}/wolips/temp/dist/ /usr/local/www/apache22/data/wolips/
Pascal Robert 118.1 98
Mike Schrag 100.1 99 {{/code}}
Pascal Robert 118.1 100
Pascal Robert 128.1 101 == Preparation for building WOLips on Windows operating systems (NT 5.0 and higher) ==
Pascal Robert 118.1 102
Pascal Robert 128.1 103 For building WOLips on Windows operating systems, some minor changes have to be made. Instead of following and solving the build errors, you may follow the steps described below.
Pascal Robert 118.1 104
Pascal Robert 128.1 105 1. Install the [[BuildingWOLips-Prerequisites>>doc:||anchor="BuildingWOLips-Prerequisites"]]. Do also follow the [[BuildingWOLips-CheckingoutandBuildinginsideofEclipseforDeployment>>doc:||anchor="BuildingWOLips-CheckingoutandBuildinginsideofEclipseforDeployment"]] section, but don't run the build until the changes described below have been made.
106 1. Set the VMs encoding to MacRoman
107 1*. Right click on {{code language="none"}}build.xml{{/code}} -> Properties -> JRE -> VM arguments
108 1**. -Dfile.encoding=MacRoman
109 1. Edit {{code language="none"}}woproject/wolips/goodies/plugins/build.xml{{/code}}
110 1*. Comment out the subsequent lines (mac goodies)
111 1**. <ant dir="org.objectstyle.wolips.goodies.core.mac" target="all" />
112 1**. <ant dir="org.objectstyle.wolips.goodies.ui.mac" target="all" />
113 1**. <ant dir="org.objectstyle.wolips.goodies.core.mac" target="dist" />
114 1**. <ant dir="org.objectstyle.wolips.goodies.ui.mac" target="dist" />
115 1. Edit {{code language="none"}}woproject/wolips/features/build.xml{{/code}}
116 1*. Comment out the subsequent lines (mac features)
117 1**. <ant dir="org.objectstyle.wolips.goodies.mac.feature" target="all" />
118 1**. <ant dir="org.objectstyle.wolips.goodies.mac.feature" target="dist" />
119 1. Edit {{code language="none"}}woproject/wolips/build.xml{{/code}} (you may skip this one if you've got JProfiler installed)
120 1*. Comment out the subsequent lines
121 1**. <ant dir="jprofiler" target="all" />
122 1**. <ant dir="jprofiler" target="dist" />
123 1. Run the build
Pascal Robert 118.1 124
Pascal Robert 128.1 125 == Installing from a Local Build ==
Pascal Robert 118.1 126
Pascal Robert 128.1 127 1. If you made changes locally, Eclipse will not automatically install your changed plugins if the version number is the same. You have two options - either uninstall WOLips or cheat and increment the WOLips build version prior to building your local copy. To uninstall WOLips, just delete all org.objectstyle features and plug ins from your eclipse folder. To increment the build server version, open buildserver.version in your projects folder and increment the last number. Note that you will now be "competing" with version numbers from the official build server, so the next official build will not install because you already used the next number, but sometimes it's a quick hack to force an update if you're lazy
128 1. Assuming you now have your build versions under control, you should follow the instructions for
129 1. Launch Eclipse
130 1. Select the menu: Help->Software Updates.
131 1. Click on the 'Available Software' tab at the top of the window.
132 1. Click on the 'Add Site...' button. This will bring up a dialog box.
133 1. Click on the 'Local...' button on the dialog box.
134 1. Browse to and select your workspace/projects/temp/dist folder or your woproject/temp/dist folder (depending on whether you checked out in eclipse or command line). Check the box next to it.
135 1. If you updated the version number in your local copy (instead of uninstalling), you must now click on the 'Installed Software' tab at the top of the window and click on the 'Update...' button.
136 1. Then continue, and just keep selecting the "Yes"/"OK"/"Approve"/etc buttons