Changes for page Building and Installing a Framework with Ant

Last modified by Pascal Robert on 2013/12/18 02:55

From 46.1 to 45.1 From 48.1 to 47.1

From version 47.1

edited by D Tim Cummings
on 2013/12/18 02:55

Change comment: There is no comment for this version

To version 46.1

edited by Steve Peery
on 2012/10/23 23:30

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.timcu
++XWiki.speery

Content

@@ -2,85 +2,39 @@
  If you use Hudson/Jenkins to build your WebObjects Frameworks and Applications, then you do not need to build or install either the Project Wonder frameworks or even your own Frameworks on your development machine, just having yours and the individual Wonder source code projects (ERJars, ERExtensions, AJAX, etc) open in your eclipse workspace is sufficient.
  {{/tip}}
++{{toc maxLevel="3"}}{{/toc}}
--
--{{toc maxLevel="3"/}}
--
  = Before You Build =
--When building a Framework project, Ant needs to be able to find WebObjects. WebObjects itself is a set of Frameworks just like the one you are building. They can be installed anywhere using [[these instructions>>doc:WO.Installing WebObjects 5\.4 on Snow Leopard]].
++When building a Framework project, Ant needs to be able to find WebObjects. WebObjects itself is a set of Frameworks just like the one you are building. They can be installed anywhere using [[these instructions>>WO:Installing WebObjects 5.4 on Snow Leopard]].
--Where Ant will look for WebObjects is specified by the {{code language="none"}}wo.system.frameworks{{/code}} build property. This property can be set in a number of locations, or even passed as a command-line property to Ant.
++Where Ant will look for WebObjects is specified by the ##wo.system.frameworks## build property. This property can be set in a number of locations, or even passed as a command-line property to Ant.
  Where Ant looks for this property is different for each method of building a Framework:
--1. (((
--====== WOJenkins Jobs ======
++1. h6. WOJenkins Jobs
++11. Completely managed for you by WOJenkins
++11. Manually overridden as defined in Manual Jenkins Jobs below.
++1. h6. Manual Jenkins Jobs
++11. Properties specified in the //Targets// line of an Invoke Ant build task using **##-D<property>=<value>##**
++11. Properties specified in the //Properties// line of an Invoke Ant build task using (the equivalent of **##-propertyfile <name>##**)
++1. h6. Eclipse/WOLips
++11. Properties specified for the Eclipse Workspace under Eclipse -> Preferences -> WOLips - > **System Frameworks**
++11. The ##build.properties## file in the same directory as the build.xml file as specified by **##<property file="build.properties" />##** task in the build.xml file.
++1. h6. Command Line
++11. Properties specified in the Ant command: **##-D<property>=<value>##**
++11. A properties file specified in the Ant command: **##-propertyfile <name>##**
++11. The ##build.properties## file in the same directory as the build.xml file as specified by **##<property file="build.properties" />##** task in the build.xml file.
--1. Completely managed for you by WOJenkins
--1. Manually overridden as defined in Manual Jenkins Jobs below.
--)))
--1. (((
--====== Manual Jenkins Jobs ======
++{{note title="Can"}}
--1. Properties specified in the //Targets// line of an Invoke Ant build task using
--
--{{code language="none"}}
---D<property>=<value>
--{{/code}}
--1. Properties specified in the //Properties// line of an Invoke Ant build task using (the equivalent of
--
--{{code language="none"}}
---propertyfile <name>
--{{/code}})
--)))
--1. (((
--====== Eclipse/WOLips ======
--
--1. Properties specified for the Eclipse Workspace under Eclipse -> Preferences -> WOLips - > **System Frameworks**
--1. The
--
--{{code language="none"}}
--build.properties
--{{/code}} file in the same directory as the build.xml file as specified by
--
--{{code language="none"}}
--<property file="build.properties" />
--{{/code}} task in the build.xml file.
--)))
--1. (((
--====== Command Line ======
--
--1. Properties specified in the Ant command:
--
--{{code language="none"}}
---D<property>=<value>
--{{/code}}
--1. A properties file specified in the Ant command:
--
--{{code language="none"}}
---propertyfile <name>
--{{/code}}
--1. The
--
--{{code language="none"}}
--build.properties
--{{/code}} file in the same directory as the build.xml file as specified by
--
--{{code language="none"}}
--<property file="build.properties" />
--{{/code}} task in the build.xml file.
--)))
--
--{{note title="Can't Find WebObjects"}}
  If Ant can't find the WebObjects frameworks, you will get compiler errors like this:
--
--{{noformat}}
++{noformat}
  [wocompile] /MyProjects/MyFramework/Sources/com/mycompany/myapp/myclass:10:
              package com.webobjects.appserver does not exist
  [wocompile] import com.webobjects.appserver.WOContext;
++{noformat}
--{{/noformat}}
  {{/note}}
  = Building =
@@ -91,69 +91,55 @@
  === Eclipse/WOLips ===
--* (((
--===== Standard WebObjects Framework =====
--
++* h5. Standard WebObjects Framework
  Right-Click on your project in Eclipse and select **WOLips Ant Tools > Install**
-- [[image:attach:WOLipsAntInstall.png]]
++[[image:WOLipsAntInstall.png||border="1"]]
  This will build and install the framework in the location defined in the WOLips preferences, overwriting any previously installed version of the framework.
  {{note title="BUILD FAILED"}}
--If Ant can't write to the WebObjects frameworks directory, you will get an error like this:
--{{noformat}}
++If Ant can't write to the WebObjects frameworks directory, you will get an error like this:
++{noformat}
  Directory /Library/WebObjects/Versions/WebObjects543/Library/Frameworks/YourFramework.framework
  creation was not successful for an unknown reason.
--
--{{/noformat}}
--
++{noformat}
  Give write access to the directory with these commands in Terminal:
-- sudo chmod 757 /Library/WebObjects/Versions/WebObjects543/Library/Frameworks/
-- sudo chmod 757 /Library/WebObjects/Versions/WebObjects543/Library/WebObjects/Applications
++sudo chmod 757 /Library/WebObjects/Versions/WebObjects543/Library/Frameworks/
++sudo chmod 757 /Library/WebObjects/Versions/WebObjects543/Library/WebObjects/Applications
++
  {{/note}}
--)))
--* (((
--===== Project Wonder Frameworks =====
--
++* h5. Project Wonder Frameworks
  **You can not build projects from Wonder this way.** You must either use the command line or Hudson/Jenkins methods
--)))
  === Command Line / Terminal ===
--You have to install woproject.jar first and make it available for ant before the following instructions will work. (see [[doc:WEB.Building a WebObjects Project||anchor="Overview"]] first)
++You have to install woproject.jar first and make it available for ant before the following instructions will work. (see [[Building a WebObjects Project||anchor="Overview"]] first)
--* (((
--===== Standard WebObjects Framework =====
--
++* h5. Standard WebObjects Framework
  You can build a standard WebObjects Framework project by calling Ant and passing it the Project directory, and the name of the build target contained in the build.xml file at your project's root.
--{{code 0="none"}}
++{{code value="none"}}
++
  cd /my/project/
  ant build
  {{/code}}
--By default, the built framework will be put in a {{code language="none"}}dist{{/code}} directory in your project's root.
--)))
++By default, the built framework will be put in a ##dist## directory in your project's root.
--* (((
--===== Project Wonder Frameworks =====
++* h5. Project Wonder Frameworks
++This assumes that you have already downloaded the Wonder source code. Make a note of the location of the Wonder directory.
++If you are building Project Wonder's frameworks you will use these commands instead:
--First download the Wonder source code (see [[doc:WEB.Getting the Wonder Source Code]]). Make a note of the location of the Wonder directory.
++{{code value="none"}}
--The Wonder build script will use properties defined in ~~/Library/Application Support/WOLips/wolips.properties. This is a good place to set {{code language="none"}}wo.system.frameworks{{/code}} property.
--
--To build Project Wonder's frameworks use these commands.
--
--{{code 0="none"}}
  cd /path/to/Wonder
  ant frameworks
  {{/code}}
--By default, all the Wonder frameworks will be built to ({{code language="none"}}~/Roots{{/code}}) (in your home directory). To build elsewhere, set the {{code language="none"}}wo.external.root{{/code}} property.
--)))
++By default, all the Wonder frameworks will be built to (##/Roots##) (in your home directory).
  = Customizing the Build =
@@ -165,21 +165,19 @@
  ===== Install the frameworks =====
--{{code 0="none"}}
--sudo ant -Duser.home=$HOME frameworks.install
++{{code value="none"}}
++sudo ant frameworks.install
  {{/code}}
--This copies the built frameworks from {{code language="none"}}~/Roots{{/code}} to the runtime Frameworks directory:
++This copies the built frameworks from ##/Roots## to the runtime Frameworks directory:
--* Mac OS X: {{code language="none"}}/Library/Frameworks/{{/code}} or {{code language="none"}}/Library/WebObjects/Versions/WebObjects543/Library/Frameworks/{{/code}}
--* Linux: {{code language="none"}}/Local/Library/Frameworks{{/code}}
++* Mac OS X: ##/Library/Frameworks/## or ##/Library/WebObjects/Versions/WebObjects543/Library/Frameworks/##
++* Linux: ##/Local/Library/Frameworks##
--Setting the {{code language="none"}}user.home{{/code}} property is necessary. Otherwise {{code language="none"}}ant{{/code}} will think {{code language="none"}}user.home{{/code}} is {{code language="none"}}/var/root{{/code}} and {{code language="none"}}frameworks.install{{/code}} would look for built frameworks in {{code language="none"}}/var/root/Roots{{/code}} and would miss any custom locations set for {{code language="none"}}wo.local.frameworks{{/code}} that are set in your {{code language="none"}}wolips.properties{{/code}} file.
--
  You can combine the build and install steps by simply executing this Ant command:
--{{code 0="none"}}
--sudo ant -Duser.home=$HOME frameworks frameworks.install
++{{code value="none"}}
++sudo ant frameworks frameworks.install
  {{/code}}
  === Upgrading ===
@@ -186,38 +186,32 @@
  This will clean out the existing versions of the frameworks. This isn't strictly necessary, you could just re-install over the top of the old frameworks, but deleting then manually copying over the new ones will clean up any old frameworks that are no longer included in the standard build.
--1. (((
--===== Navigate to the original Wonder source directory that you created above during initial source installation =====
++1. h5. Navigate to the original Wonder source directory that you created above during initial source installation
--{{code 0="none"}}
++{{code value="none"}}
  cd /path/to/WonderSource
  {{/code}}
--)))
--1. (((
--===== Pull the changes you do not have and merge them with your local repository =====
--{{code 0="none"}}
++1. h5. Pull the changes you do not have and merge them with your local repository
++
++{{code value="none"}}
  git pull
  {{/code}}
--)))
--1. (((
--===== Build the frameworks. =====
--{{code 0="none"}}
++1. h5. Build the frameworks.
++
++{{code value="none"}}
  ant frameworks
  {{/code}}
--)))
--1. (((
--===== Navigate to the Roots directory that was automatically created by the initial Source installation procedure above =====
--{{code 0="none"}}
++1. h5. Navigate to the Roots directory that was automatically created by the initial Source installation procedure above
++
++{{code value="none"}}
  cd ~/Roots/
  {{/code}}
--)))
--1. (((
--===== Delete all installed frameworks whose names match the built frameworks in this Roots build folder =====
--{{code 0="none"}}
++1. h5. Delete all installed frameworks whose names match the built frameworks in this Roots build folder
++
++{{code value="none"}}
  for FRAMEWORK in `echo *.framework`; do sudo rm -r /Library/Frameworks/${FRAMEWORK}; done
  {{/code}}
--)))

Changes for page Building and Installing a Framework with Ant

Summary

Details

Applications

Navigation

My Recent Modifications

Need help?