-------- Original Message --------
Subject: Re: Using WOProject and ant to build WO Apps
From: "Andrus Adamchik" <andrus-w..bjectstyle.org>
Date: Mon, July 14, 2003 9:01 pm
To: <jerry.porte..rx-ca.com>
[cc: woproject-dev]
Hi Jerry,
> Thanks for the reply,
>
> I don't mind making a fix myself to the code base and submit the
> change.
> I am guessing that WOProject is just getting the class path txt files
> from templates and appending the classpaths before writing the files
> to the app wrapper.
Yes. Templates are located under woproject/src/resources. They have
tokens that are substituted during the build, e.g...PP_JAR@.. So your's
would be..VM_OPTIONS@ (this is consistent with how Ant filtersets work,
and this is actually what is being used in the backend).
> I would like to know the best way to insert the
> arguments for the various properties I would like to set in the
> classpath txt files, primarily the JVM_OPTIONS property.
I haven't investigated other options, but for JVM_OPTIONS I suggest to
mimic Ant "Java" task and create an extra (optional) task parameter
called "jvmargs". The value for this property can be supplied in the Ant
buildfile just like any other string - either by hardcoding it, or using
a property value. But the point is that from WOApplication Ant Task
standpoint, there will be no assumptions about the environemnt, and
arguments will be taken from parameter.
To add an extra parameter to a task, all that is needed is a set method
(see Ant docs on how to write a task and WOApplication source). For
token substitution logic see AppFormat and ProjectFormat classes.
I am taking a long vacation in about a week, so if you send a patch, it
may take a while to apply. In any event, start by sending it to the
woproject-dev list. Someone else may volunteer to apply it.
Thanks!
Andrus
This archive was generated by hypermail 2.0.0 : Mon Jul 14 2003 - 21:02:35 EDT