Changes for page Building a WebObjects Project

Summary

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

Details

Page properties

Content

...	...	@@ -7,24 +7,26 @@
7	7
8	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:
9	9
10		-1. **[[woproject.jar>>url:http://webobjects.mdimension.com/hudson/job/WOLips36Stable/lastSuccessfulBuild/artifact/||shape="rect"]]**
11		- The {{code language="none"}}woproject.jar{{/code}} library is embedded in WOLips to help Eclipse, Ant (when triggered from within Eclipse) and Maven build a valid WebObjects Application ({{code language="none"}}.woa{{/code}}) or WebObjects Framework ({{code language="none"}}.framework{{/code}}) bundle. If you are going to build your project using Hudson/Jenkins, then it will also need access to this library
12		-1. **[[doc:documentation.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. **[[doc: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**: {{code language="none"}}~/Users/yourusername/Library/Application Support/WOLips/wolips.properties{{/code}}
17		-1*. **Linux**: {{code language="none"}}/home/<user>/Library/Application Support/WOLips/wolips.properties{{/code}}
18		-1*. **Windows**: {{code language="none"}}C:\Documents and Settings\<user>\Library\Application Support\WOLips\wolips.properties{{/code}}
	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. **[[WO: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##
19	19
20	20	= Incremental Building =
21	21
22	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.
23	23
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 As — > WO Application** or **Debug As — > WO 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 {{code language="none"}}.woa{{/code}} or {{code language="none"}}.framework{{/code}} bundle. The Incremental Builder does not use Ant or Maven.
	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.
25	25
26		-{{info title="Incremental Builds != Ant/Maven Builds"}}
27		-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.
	26	+{{info title="Incremental Builds !"}}
	27	+
	28	+Just because your project runs fine in Eclipse/WOLips does not necessarily mean it will build or run, when using Ant or Maven (for deployment). 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.
	29	+
28	28	{{/info}}
29	29
30	30	= Deployment Building =