There are two different and very distinct kinds of builds for a WebObjects project.
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:
woproject.jarlibrary 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
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.
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:
- Mac OS X:
C:\Documents and Settings\<user>\Library\Application Support\WOLips\wolips.properties
- Mac OS X:
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. You can launch your applications from within WOLips/Eclipse 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
.framework bundle. The Incremental Builder does not use Ant or Maven. Just because your project runs fine in Eclipse/WOLips does not necessarily mean it will build, let alone run, when using Ant or Maven.
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.
The process and options vary slightly between Frameworks and Applications, but they share many fundamental concepts.