Sorry.
I've implemented it only for maven. Don't have the time to backport
it to ant.
Uli
Am 09.08.2007 um 19:55 schrieb Kieran Kelleher:
> Ah, OK Ulrich .... I was very wishfully thinking that using
> frameworksBaseURL might trigger an embedded split install of apps
> wsresources and all framework webserver resources since the
> combined use of embed=true and declaration of wsDestDir did not do it.
>
> Is there already existing woproject tasks/params I can define in
> the standard build.xml to make the embedded split install or must
> do I need to roll my own?
>
> Kieran
>
> On Aug 9, 2007, at 12:59 PM, Ulrich Köster wrote:
>
>> We use it for maven builds to change the WOFrameworkBaseURL. It's
>> a parameter in the launch script.
>>
>> From the launch script template
>>
>> echo Launching ${SCRIPT_NAME}.woa ...
>>
>> echo ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath
>> WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap $
>> {COMMAND_LINE_ARGS}..WOFrameworksBaseURL@
>> eval exec ${JAVA_EXECUTABLE} ${JAVA_EXECUTABLE_ARGS} -classpath
>> WOBootstrap.jar com.webobjects._bootstrap.WOBootstrap $
>> {COMMAND_LINE_ARGS}..WOFrameworksBaseURL@
>>
>>
>> You could search this list for more details.
>>
>> Uli
>> Am 09.08.2007 um 17:54 schrieb Kieran Kelleher:
>>
>>> what does woapplication task's "frameworksBaseURL" attribute do?
>>>
>>> It does not seem to do anything?
>>>
>>> Kieran
>>
>
This archive was generated by hypermail 2.0.0 : Thu Aug 09 2007 - 14:01:49 EDT