Updated Apr 20, 2008 by ste...@e-nation.dk
Labels:	Phase-Support, Featured

OcbuildQnA

Changelog for ocbuild

Questions and Answers

I keep getting the "Please define build.conf" message, what's wrong?

First ensure that the build.conf property is set (or ignore this step, if you are just using the default value buildconf/default)
Secondly be sure that the files filter.properties and deploy.properties are both in the folder.

If you haven't defined the build.conf property, but don't want to use the default path, you can specify the property using ant's -D parameter. This can be done via the command line when running ant:

ant Synchronize -Dbuild.conf=/path/to/your/buildconf/dir

or relative the the project directory

ant Synchronize -Dbuild.conf=buildconf/mybuildconf

If you are an eclipse user, please see the OcbuildUsingEclipse article.

My property changes are not affecting OpenCms, why?

As also mentioned in the OcbuildHowTo article, properties in OpenCms are subject to cache, so if OpenCms runs in tomcat, the properties you update outside tomcat are not re-read from the database, until tomcat is restarted.

The solution is to restart tomcat (or whatever servlet container you are running). Sorry.

A fix for this issue is a work in progress. I would like to have a buildserver module for OpenCms that, on OpenCms startup, listens for build commands. In effect, there will only be one instance of OpenCms running, thus solving the cache problem.

How can I create siblings using ocbuild?

Ease! Since everything is controlled by the properies generated by ocbuild (found in vfs/properties), you can create your own properties file for each sibling you want to create. Take a copy of the existing properties file of which you would like to make a sibling.

Lets say you want to make a sibling of page_frontpage.jsp called page_subpage.jsp. The properties file for page_frontpage.jsp could look like this:

page_frontpage.jsp.properties

# Generated by Valtech BuildTool
# Sat Dec 22 15:25:14 CET 2007
f.source=system/modules/dk.valtech.templateproject/templates/page_frontpage.jsp
f.destination=system/modules/dk.valtech.templateproject/templates/page_frontpage.jsp
f.uuidstructure=eeb3e79b-b1a5-11dc-b078-afbb2816dba9
f.uuidresource=eeb3e79c-b1a5-11dc-b078-afbb2816dba9
f.type=jsp
f.datecreated=1198448714690
f.usercreated=Admin
f.userlastmodified=Admin
f.flags=0

# Shared properties (r = resource = shared)
r.export=false
r.template-elements=body|Main body content

# Individual properties (s = (file) structure = individual)
s.Title=Front page template

Now make a copy of the page_frontpage.jsp.properties file. Name it page_subpage.jsp.properties. You must then do two things:

Change the f.destination property to point to the destination of your sibling.
Delete the line with the f.uuidstructure property (since this id refers the the file structure entry of the original file)

The file could look like this after the above changes:

page_subpage.jsp.properties

# Generated by Valtech BuildTool
# Sat Dec 22 15:25:14 CET 2007
f.source=system/modules/dk.valtech.templateproject/templates/page_frontpage.jsp
f.destination=system/modules/dk.valtech.templateproject/templates/page_subpage.jsp
f.uuidresource=eeb3e79c-b1a5-11dc-b078-afbb2816dba9
f.type=jsp
f.datecreated=1198448714690
f.usercreated=Admin
f.userlastmodified=Admin
f.flags=0

# Shared properties (r = resource = shared)
r.export=false
r.template-elements=body|Main body content

# Individual properties (s = (file) structure = individual)
s.Title=Sub page template

Now when you run the Synchronize task again, a sibling of page_frontpage.jsp will be created into page_subpage.jsp and the page_subpage.jsp.properties file will be updated to include the new structure id of the sibling in the f.uuidstructure property, which is needed for manifest file generation.