Changes for page Building a WebObjects Project

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,39 +1,39 @@
1		-== Incremental Building ==
	1	+= Overview =
2	2
3		-=== ===
	3	+There are two different and very distinct kinds of builds used during the development and deployment of a WebObjects project.
4	4
5		-While you are writing your classes and Components (.html, .wod, etc.) the incremental builder is constantly running in the background compiling and validating your code against your projects other code and its dependencies. Building WebObjects Frameworks and Applications during development is handled directly by Eclipse/WOLips using the Incremental Builder that by default automatically compiles and validates your classes and components as you type. You can launch your applications from within WOLips/Eclipse with no need to compile or install any source code frameworks in the workspace that they depend on.
	5	+1. **Incremental Build** - this is what Eclipse does every time you save a file. It's automatic (unless you turn it off) and it is very unlikely you'll ever need to really think about it.
	6	+1. **Deployment Build** - this is what **you** need to do every time you want to deploy your application. Often times you will customize this process if you are doing things differently than the defaults.
6	6
7		-== Deployment Building ==
	8	+Both Incremental and Deployment builds make use of some common files to tell them where to look for resources needed to build an application or framework. They include:
8	8
9		-=== ===
	10	+1. **[[woproject.jar>>http://webobjects.mdimension.com/hudson/job/WOLips36Stable/lastSuccessfulBuild/artifact/]]**
	11	+The ##woproject.jar## library is embedded in WOLips to help Eclipse, Ant (when triggered from within Eclipse) and Maven build a valid WebObjects Application (##.woa##) or WebObjects Framework (##.framework##) bundle. If you are going to build your project using Hudson/Jenkins, then it will also need access to this library
	12	+1. **[[The build.properties File]]**
	13	+This file resides in the root directory your WebObjects project. It may be hidden from your view by Eclipse's ability to filter the displayed files in the //WO Explorer// view, but if you look in the project's directory in the finder/desktop/command line you will see it.
	14	+1. **[[WOL:wolips.properties]]**
	15	+This file can contain and override the same settings as the build.properties file, but it's primary purpose is to define the locations that a build done by Eclipse or Ant will look for compiled framework dependencies in. The default location of this file is:
	16	+1*. **Mac OS X**: ##/Users/yourusername/Library/Application Support/WOLips/wolips.properties##
	17	+1*. **Linux**: ##/home/<user>/Library/Application Support/WOLips/wolips.properties##
	18	+1*. **Windows**: ##C:ocuments and Settingsuser>ibrarypplication SupportOLipsolips.properties##
10	10
11		-The process of building WebObjects Applications and Frameworks for Deployment is more complicated and requires any depended-upon frameworks to already be compiled and installed in defined (but customizable) locations. Building and Installing of both Frameworks and Applications can be also be done directly in Eclipse, but it can also be done from the Command Line or better yet, using a Continuous Integration Server like Hudson/Jenkins. Use of Hudson/Jenkins to build your Applications is **highly** recommended.
	20	+= Incremental Building =
12	12
13		-The process and options vary slightly between Frameworks and Applications, but they share many fundamental concepts.
	22	+While you are writing your classes and Components (.html, .wod, etc.) the incremental builder is running in the background continuously compiling and validating your code against your projects other code and dependencies. The only time it isn't running is when you turn off "Build Automatically" in Eclipse under the Project menu.
14	14
15		-1. build.properties file
	24	+When you are building automatically, you can launch your application at any time from within WOLips/Eclipse by right-clicking on the project and selecting either **Run&nbsp;As ~-~-- > WO&nbsp;Application** or **Debug&nbsp;As ~-~-- > WO&nbsp;Application** with no need to manually compile or install any source code either from your current project, or from any frameworks in the workspace that your project depends upon. WOLips/Eclipse takes care of resolving dependencies for things that are not in the locations they will be in in a deployed ##.woa## or ##.framework## bundle. The Incremental Builder does not use Ant or Maven.
16	16
17		-{{code title="Example Application build.properties File"}}
	26	+{{info title="Incremental Builds !"}}
18	18
19		-classes.dir=bin
20		-component.inlineBindingPrefix=$
21		-component.inlineBindingSuffix=
22		-component.wellFormedTemplateRequired=false
23		-customInfoPListContent=
24		-embed.Local=true
25		-embed.Project=true
26		-embed.System=true
27		-eoAdaptorClassName=
28		-principalClass=com.company.MyApp.Application.java
29		-project.name=MyApp
30		-project.name.lowercase=myapp
31		-project.type=application
32		-webXML=false
33		-webXML_CustomContent=
	28	+Just because your project runs fine in Eclipse/WOLips does not necessarily mean it will build when using Ant or Maven. If you haven't made changes to the defaults and are doing a standard deployment then it should just work, but if you've modified install locations or are using source (as opposed to binary) frameworks then you will likely have additional steps that you'll need to do complete prior to being able to use Ant or Maven to build.
34	34
35		-{{/code}}
	30	+{{/info}}
36	36
37		-1. wolips.properties file
	32	+= Deployment Building =
38	38
39		-{{pagetree root="@self"}}{{/pagetree}}
	34	+The process of building WebObjects Applications and Frameworks for Deployment is more complicated and requires any depended-upon frameworks to already be compiled and installed in defined (but customizable) locations. Building and Installing of both Frameworks and Applications can be also be done directly in Eclipse, but it can also be done from the Command Line or better yet, using a Continuous Integration Server like Hudson/Jenkins. Use of Hudson/Jenkins to build your Applications is **highly** recommended.
	35	+
	36	+The process and options vary slightly between Frameworks and Applications, but they share many fundamental concepts.
	37	+
	38	+* Building WO Frameworks using Ant
	39	+* Building WO Applications using Ant