Skip to Content

Changes for page Installing WOLips

Last modified by Denis Frolov on 2011/12/05 09:55
From version 83.1
edited by Mike Schrag
on 2006/03/03 09:24
Change comment: There is no comment for this version
To version 87.1
edited by Mike Schrag
on 2006/05/14 08:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,31 +1,10 @@
1 -You have three options for installing WOLips.
1 +== "Quick" Install ==
2 2  
3 -The first is to grab the latest stable build from the [[WOLips/WOProject Site>>http://objectstyle.org/woproject/]]. You can then just install it liike any other Eclipse plugin. However, you are getting a version of the code that is pretty old now.
3 +The easiest way to install WOLips is to follow the steps in the [[Install WOLips with Eclipse Update Manager]] tutorial.
4 4  
5 -The second way is to grab one of the Nightly Builds. Nightly builds are built from the latest-and-greatest source at the head of the CVS tree.
6 -
7 -Lastly you can instead [[build WOLips>>Building WOLips]] yourself and enjoy the latest and greatest features and bugfixes. This is basically the same as the nightly builds, but do-it-yourself.
8 -
9 -== WOLips Dependencies ==
10 -
11 -Recent version of WOLips in CVS have more extensive dependencies than prior builds (mostly due to the HTML editor that is part of the web tools project).
12 -
13 -Additionally you will need to download and install Eclipse 3.2, a build of Eclipse that does not currently have an official release.
14 -
15 -You can get a 3.2 build from [[Eclipse.org>>http://download.eclipse.org/eclipse/downloads/index.php]].
16 -
17 -After installing Eclipse 3.2 and before building or installing WOLips, you will need to download, unzip the following plugins and features, and copy the corresponding plugins and features into your eclipse plugins and features folders:
18 -
19 -* [[EMF>>http://www.mdimension.com/~~wolips/dependencies/emf-sdo-xsd-SDK-2.1.1.zip]]
20 -* [[GEF>>http://www.mdimension.com/~~wolips/dependencies/GEF-SDK-3.1.1.zip]]
21 -* [[JEM>>http://www.mdimension.com/~~wolips/dependencies/JEM-SDK-1.1.0.1.zip]]
22 -* [[WTP>>http://www.mdimension.com/~~wolips/dependencies/wtp-sdk-1.0-webobjects.zip]]
23 -* [[TPTP>>http://www.mdimension.com/~~wolips/dependencies/tptp.runtime-TPTP-4.1.0.zip]]
24 -* [[jMechanic>>http://www.mdimension.com/~~wolips/dependencies/jmechanic.eclipse.profiler-0.6.0.zip]]
25 -
26 26  == WOLips Nightly Build Server ==
27 27  
28 -Nightly builds of WOLips are maintained in several forms at http:~/~/www.mdimension.com/~~wolips/. Among the various packagings you will find are:
7 +If you already have WOLips' dependencies (WTP, TPTP, GEM, and GEF), then you can download WOLips from the build server. Nightly builds of WOLips are maintained in several forms at http:~/~/www.mdimension.com/~~wolips/. Among the various packagings you will find are:
29 29  
30 30  * http:~/~/www.mdimension.com/~~wolips/dependencies/
31 31  This folder contains all the zips for the dependencies of wolips (so you don't have to go through all those damn sites)
... ... @@ -45,10 +45,8 @@
45 45  1. Download an Eclipse 3.2 and uncompress it into a folder
46 46  1. Download the http:~/~/www.mdimension.com/~~wolips/wolips-all-latest.tar.gz latest WOLips
47 47  1. Uncompress the WOLips tar.gz in the same folder you uncompressed Eclipse 3.2 in
48 -1. Run
27 +1. Profit :)
49 49  
50 -Alternatively, you can install WOLips following the steps in the [[Install WOLips with Eclipse Update Manager]] tutorial.
51 -
52 52  == Installing from a Local Build ==
53 53  
54 54  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 plugins 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 :)