Skip to Content

Changes for page Building WOLips

Last modified by Johann Werner on 2015/02/13 01:40
From version 51.1
edited by Pascal Robert
on 2012/02/11 08:50
Change comment: There is no comment for this version
To version 59.1
edited by Pascal Robert
on 2010/10/03 00:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,8 +6,3 @@
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/]
3 -
4 -{{/tip}}
5 -
6 6  {{note}}
7 7  
8 8  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 [Debugging WOLips].
... ... @@ -11,20 +11,26 @@
11 11  
12 12  Prior to building WOLips, you will want to get your dependencies installed properly. Check out the [[Installing WOLips]] page for information on the dependencies for WOLips.
13 13  
14 -{{color value="#000000"}}
15 -{*}Prerequisites{*}
16 -{{/color}}
9 +WOLips is now located in Subversion at ##objectstyle.org##. The CVS repository at sourceforge is now deprecated.
17 17  
18 -==== Install eGit or another Git client ====
11 +The subversion repository path is https:~/~/svn.objectstyle.org/repos/woproject
19 19  
20 -See [[Getting Started With Git>>documentation:Getting Started with Git]] for information on how to obtain a Git client.
13 +== Prerequisites ==
21 21  
15 +==== Install Subclipse (the Subversion plugins) ====
16 +
17 +1. Help=>Software Updates=>Find and Install ...
18 +1. Add New Remote Site
19 +11. Name = Subclipse
20 +11. URL = http:~/~/subclipse.tigris.org/update_1.0.x
21 +1. Select the site, select all the plugins available, and install them
22 +
22 22  ==== Install the m2eclipse plugin (Eclipse 3.5 instructions) ====
23 23  
24 -1. Help > Install New Software
25 -1. Click "Add..."
25 +1. Help -> Install New Software
26 +1. Click "Add..."
26 26  11. Name = M2Eclipse
27 -11. Location = [[http://m2eclipse.sonatype.org/update/]]
28 +11. Location = http:~/~/m2eclipse.sonatype.org/update/
28 28  11. Click "OK"
29 29  1. Expand "Maven Integration"
30 30  1. Select "Maven Embedder"
... ... @@ -35,26 +35,21 @@
35 35  == Checking out and Building from the Commandline ==
36 36  
37 37  1. Checkout the ##trunk/woproject## folder from Subversion
38 -##git clone## ##[[git://github.com/wolips/wolips.git]]## woproject
39 +##svn co https:~/~/svn.objectstyle.org/repos/woproject/trunk .##
39 39  1. ##cd woproject##
40 40  1. ##ant##
41 41  1. The first build will fail out telling you that it couldn't find ##wobuild.properties## ~-~- That's OK
42 -1. Edit ##/Library/wobuild.properties##
43 +1. Edit ##,,/Library/wobuild.properties,,##
43 43  1. Add a line: ##eclipse.home=/path/to/your/eclipse##
44 -1. Call ant with the build.version argument:
45 -
46 -{{code}}
47 -ant -Dbuild.version=3.7.SomeNumber
48 -{{/code}}
49 -
50 -1.
51 -11. If you get the error ##'build.xml:73: taskdef A class needed by class org.apache.velocity.anakia.AnakiaTask cannot be found: org/jdom/JDOMException'##, you can do one of two things. You can build with ##Dno.docs=true## to skip the javadoc step, or (untested) you can drop ##jdom-b8.jar## from ##woproject/projects/lib## into your ##ANT//HOME/lib//##// folder.//
45 +1. ant again and it should succeed this time
46 +11. If you get the error ##'build.xml:73: taskdef A class needed by class org.apache.velocity.anakia.AnakiaTask cannot be found: org/jdom/JDOMException'##, you can do one of two things. You can build with ##-Dno.docs=true## to skip the javadoc step, or (untested) you can drop ##jdom-b8.jar## from ##woproject/projects/lib## into your ##ANT//HOME/lib//##// folder.//
52 52  1. The build went into ##temp/dist##
53 53  1. Profit
54 54  
55 55  == Checking out and Building inside of Eclipse for Deployment ==
56 56  
57 -1. Add the wolips Git repository [[https://github.com/wolips/wolips/]] in the Git Perspective's Repository View
52 +1. Add the wolips SVN repository https:~/~/svn.objectstyle.org/repos/woproject in the SVN Perspective's Repository View
53 +1. In SVN perspective, browse WOLips repository on HEAD, checkout ##trunk/woproject##
58 58  1. Right-click (or equiv) on the ##build.xml## inside of the "woproject" project and Run As=>Ant Build ...
59 59  1. Switch to the Properties tab and check for the definition of eclipse.home in the Properties list
60 60  1. If ##eclipse.home## does not exist, uncheck "Use global properties" and then click "Add Property"
... ... @@ -65,7 +65,7 @@
65 65  
66 66  == Checking out and Building inside of Eclipse for Development (PDE) ==
67 67  
68 -1. Add the wolips Git repository [[https://github.com/wolips/wolips/]] in the Git Perspective's Repository View
64 +1. Add the wolips SVN repository https:~/~/svn.objectstyle.org/repos/woproject in the SVN Perspective's Repository View
69 69  1. You can select individual plugins you would like to work on by browsing to ##trunk/woproject/wolips/## in the Subversion repository and checking out the plugins you are interested in. To checkout complete sets of plugins, you could also use the [[Eclipse Team Project Set]].
70 70  
71 71  == An approach to setting up the development and test environment for WOLips Plugin. ==
... ... @@ -78,29 +78,25 @@
78 78  1. In the test environment, follow the [[Installing WOLips]] instructions, using your ##temp/dist## directory as the Local Site. Install the plugins.
79 79  1. Use the Test environment to exercise/test the changes from your locally modified Plugin.
80 80  
81 -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.
77 +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.**
82 82  
83 -== Building WOLips with Jenkins Continuous Build server ==
79 +== Building WOLips with Hudson Continuous Build server ==
84 84  
85 85  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.
86 86  
87 -1. Install Eclipse 3.7. You need it to be able to build WOLips.
88 -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
89 -The currently required plugins for a deployment build are
90 - JProfiler (Update Site:&nbsp;[[http://wocommunity.org/documents/tools/jprofiler6/]])
91 - JRebel (Update Site :&nbsp;[[http://www.zeroturnaround.com/update-site/]])
92 -1. Create a new job in Jenkins to build WOLips. You can use the [[following sample config>>https://github.com/wocommunity/JenkinsJobs/tree/master/WOLips]]&nbsp;or you can add a new job with the following configuration:
93 -11. Project Name: WOLips
94 -11. Git Repositories:&nbsp;git:~/~/github.com/wolips/wolips.git
95 -11. Use update: Checked
96 -11. Poll SCM: 59 * ** * ** //(59 can be replaced with any number between 0 and 59)//
83 +1. Add a new job with the following configuration
84 + Project Name: WOLips
85 + Subversion: http:~/~/svn.objectstyle.org/repos/woproject/trunk/woproject
86 + Local module directory (optional): wolips
87 + Use update: Checked
88 + Poll SCM: 59 * ** * ** //(59 can be replaced with any number between 0 and 59)//
97 97  1. Add the following build tasks to the job
98 98  
99 99  {{code title="Execute Shell"}}
100 100  
101 -echo build.version=3.7.${BUILD_NUMBER} > build.properties
102 -echo eclipse.home=/usr/local/eclipse >> build.properties
103 -echo user.home=${WORKSPACE} >> build.properties
93 +echo build.version=3.4.${SVN_REVISION} > wolips/build.properties
94 +echo eclipse.home=/usr/local/eclipse >> wolips/build.properties
95 +echo user.home=${WORKSPACE} >> wolips/build.properties
104 104  
105 105  {{/code}}
106 106  
... ... @@ -119,28 +119,47 @@
119 119  
120 120  {{/code}}
121 121  
114 +1. Copy eclipse with the necessary plugins installed to your build server. In this example it has been copied to /usr/local/eclipse
115 +The currently required plugins for a deployment build are
116 +
117 +*
118 +** JProfiler
119 +** m2Eclipse Maven
120 +
122 122  == Preparation for building WOLips on Windows operating systems (NT 5.0 and higher) ==
123 123  
124 124  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.
125 125  
126 -1. Install the [[BuildingWOLips-Prerequisites>>||anchor="BuildingWOLips-Prerequisites"]]. Do also follow the [[BuildingWOLips-CheckingoutandBuildinginsideofEclipseforDeployment>>||anchor="BuildingWOLips-CheckingoutandBuildinginsideofEclipseforDeployment"]] section, but don't run the build until the changes described below have been made.
125 +1. Install the [[||anchor="BuildingWOLips-Prerequisites"]]. Do also follow the [[||anchor="BuildingWOLips-CheckingoutandBuildinginsideofEclipseforDeployment"]] section, but don't run the build until the changes described below have been made.
127 127  1. Set the VMs encoding to MacRoman
128 -1*. Right click on ##build.xml## > Properties > JRE > VM arguments
129 -1**. Dfile.encoding=MacRoman
127 +
128 +*
129 +** Right click on ##build.xml## -> Properties -> JRE -> VM arguments
130 +*** --Dfile.encoding=MacRoman--
131 +
130 130  1. Edit ##woproject/wolips/goodies/plugins/build.xml##
131 -1*. Comment out the subsequent lines (mac goodies)
132 -1**. <ant dir="org.objectstyle.wolips.goodies.core.mac" target="all" />
133 -1**. <ant dir="org.objectstyle.wolips.goodies.ui.mac" target="all" />
134 -1**. <ant dir="org.objectstyle.wolips.goodies.core.mac" target="dist" />
135 -1**. <ant dir="org.objectstyle.wolips.goodies.ui.mac" target="dist" />
133 +
134 +*
135 +** Comment out the subsequent lines (mac goodies)
136 +*** <ant dir="org.objectstyle.wolips.goodies.core.mac" target="all" />
137 +*** <ant dir="org.objectstyle.wolips.goodies.ui.mac" target="all" />
138 +*** <ant dir="org.objectstyle.wolips.goodies.core.mac" target="dist" />
139 +*** <ant dir="org.objectstyle.wolips.goodies.ui.mac" target="dist" />
140 +
136 136  1. Edit ##woproject/wolips/features/build.xml##
137 -1*. Comment out the subsequent lines (mac features)
138 -1**. <ant dir="org.objectstyle.wolips.goodies.mac.feature" target="all" />
139 -1**. <ant dir="org.objectstyle.wolips.goodies.mac.feature" target="dist" />
142 +
143 +*
144 +** Comment out the subsequent lines (mac features)
145 +*** <ant dir="org.objectstyle.wolips.goodies.mac.feature" target="all" />
146 +*** <ant dir="org.objectstyle.wolips.goodies.mac.feature" target="dist" />
147 +
140 140  1. Edit ##woproject/wolips/build.xml## (you may skip this one if you've got JProfiler installed)
141 -1*. Comment out the subsequent lines
142 -1**. <ant dir="jprofiler" target="all" />
143 -1**. <ant dir="jprofiler" target="dist" />
149 +
150 +*
151 +** Comment out the subsequent lines
152 +*** <ant dir="jprofiler" target="all" />
153 +*** <ant dir="jprofiler" target="dist" />
154 +
144 144  1. Run the build
145 145  
146 146  == Installing from a Local Build ==