Wiki source code of Building WOLips
Version 125.1 by mark_ritchie on 2009/08/30 14:08
Show last authors
author | version | line-number | content |
---|---|---|---|
1 | 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. | ||
2 | |||
3 | WOLips is now located in Subversion at ##objectstyle.org##. The CVS repository at sourceforge is now deprecated. | ||
4 | |||
5 | The subversion repository path is https:~/~/svn.objectstyle.org/repos/woproject | ||
6 | |||
7 | == Prerequisites == | ||
8 | |||
9 | ==== Install Subclipse (the Subversion plugins) ==== | ||
10 | |||
11 | 1. Help=>Software Updates=>Find and Install ... | ||
12 | 1. Add New Remote Site | ||
13 | 11. Name = Subclipse | ||
14 | 11. URL = http:~/~/subclipse.tigris.org/update_1.0.x | ||
15 | 1. Select the site, select all the plugins available, and install them | ||
16 | |||
17 | ==== Install the m2eclipse plugin (Eclipse 3.5 instructions) ==== | ||
18 | |||
19 | 1. Help -> Install New Software | ||
20 | 1. Click "Add..." | ||
21 | 11. Name = M2Eclipse | ||
22 | 11. Location = http:~/~/m2eclipse.sonatype.org/update/ | ||
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 | |||
30 | == Checking out and Building from the Commandline == | ||
31 | |||
32 | 1. Checkout the ##trunk/woproject## folder from Subversion | ||
33 | ##svn co https:~/~/svn.objectstyle.org/repos/woproject/trunk .## | ||
34 | 1. ##cd woproject## | ||
35 | 1. ##ant## | ||
36 | 1. The first build will fail out telling you that it couldn't find ##wobuild.properties## ~-~- That's OK | ||
37 | 1. Edit ##,,/Library/wobuild.properties,,## | ||
38 | 1. Add a line: ##eclipse.home=/path/to/your/eclipse## | ||
39 | 1. ant again and it should succeed this time | ||
40 | 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.// | ||
41 | 1. The build went into ##temp/dist## | ||
42 | 1. Profit | ||
43 | 1. [[Installing WOLips]] | ||
44 | |||
45 | == Checking out and Building inside of Eclipse for Deployment == | ||
46 | |||
47 | 1. Add the wolips SVN repository https:~/~/svn.objectstyle.org/repos/woproject in the SVN Perspective's Repository View | ||
48 | 1. In SVN perspective, browse WOLips repository on HEAD, checkout ##trunk/woproject## | ||
49 | 1. Right-click (or equiv) on the ##build.xml## inside of the "woproject" project and Run As=>Ant Build ... | ||
50 | 1. Switch to the Properties tab and check for the definition of eclipse.home in the Properties list | ||
51 | 1. If ##eclipse.home## does not exist, uncheck "Use global properties" and then click "Add Property" | ||
52 | 1. In the Add Property dialog, make the name ##eclipse.home##, click Add Variable, select ##eclipse//home//##// from the list, and click OK// | ||
53 | 1. Click Apply to save your changes | ||
54 | 1. Run | ||
55 | 1. Once it is complete, you may need to right-click=>refresh your project and you will have a ##temp/dist## folder with the plugin site in it. | ||
56 | 1. [[Installing WOLips]] | ||
57 | |||
58 | == Checking out and Building inside of Eclipse for Development (PDE) == | ||
59 | |||
60 | 1. Add the wolips SVN repository https:~/~/svn.objectstyle.org/repos/woproject in the SVN Perspective's Repository View | ||
61 | 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]]. | ||
62 | |||
63 | == An approach to setting up the development and test environment for WOLips Plugin. == | ||
64 | |||
65 | In order to do WOLips Plugin development you will need two eclipse environments: Development and Test. | ||
66 | |||
67 | 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. | ||
68 | 1. the ##temp/dist## folder is your Local Site for the Test Environment. | ||
69 | 1. Create a second copy of "clean" Eclipse under /Users/<me>/Developer/eclipse (this could be any where). This will be your Test Environment. | ||
70 | 1. In the test environment, follow the [[Installing WOLips]] instructions, using your ##temp/dist## directory as the Local Site. Install the plugins. | ||
71 | 1. Use the Test environment to exercise/test the changes from your locally modified Plugin. | ||
72 | |||
73 | 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.** | ||
74 | |||
75 | == Building WOLips with Hudson Continuous Build server == | ||
76 | |||
77 | 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. | ||
78 | |||
79 | 1. Add a new job with the following configuration | ||
80 | Project Name: WOLips | ||
81 | Subversion: http:~/~/svn.objectstyle.org/repos/woproject/trunk/woproject | ||
82 | Local module directory (optional): wolips | ||
83 | Use update: Checked | ||
84 | Poll SCM: 59 * ** * ** //(59 can be replaced with any number between 0 and 59)// | ||
85 | 1. Add the following build tasks to the job | ||
86 | |||
87 | {{code title="Execute Shell"}} | ||
88 | |||
89 | echo build.version=3.4.${SVN_REVISION} > wolips/build.properties | ||
90 | echo eclipse.home=/usr/local/eclipse >> wolips/build.properties | ||
91 | echo user.home=${WORKSPACE} >> wolips/build.properties | ||
92 | |||
93 | {{/code}} | ||
94 | |||
95 | {{code title="Invoke Ant"}} | ||
96 | |||
97 | Targets: dist | ||
98 | |||
99 | {{/code}} | ||
100 | |||
101 | 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 | ||
102 | |||
103 | {{code title="Execute Shell"}} | ||
104 | |||
105 | rm -fr /usr/local/www/apache22/data/wolips/* | ||
106 | /bin/cp -prv ${WORKSPACE}/wolips/temp/dist/ /usr/local/www/apache22/data/wolips/ | ||
107 | |||
108 | {{/code}} | ||
109 | |||
110 | 1. Copy eclipse with the necessary plugins installed to your build server. In this example it has been copied to /usr/local/eclipse | ||
111 | The currently required plugins for a deployment build are | ||
112 | |||
113 | * | ||
114 | ** JProfiler | ||
115 | ** m2Eclipse Maven |