My mistake, it does seem to work correctly.
Alan
On 7-Sep-06, at 11:48 AM, Alan Zebchuk wrote:
> It looks like there's a bug whereby if you put the embed="true" it
> will embed all the ones in the root directory, not just the ones
> included in any patternset defined.
>
> For example:
> <frameworks root="${wo.wolocalroot}" embed="true">
> <patternset>
> <includesfile name="woproject/ant.frameworks.wo.wolocalroot"/>
> </patternset>
> </frameworks>
>
>
> This will cause all of the frameworks in ${wo.wolocalroot} to be
> embedded.
>
> Alan
>
>
> On 7-Sep-06, at 9:52 AM, Ulrich Köster wrote:
>
>> The embed="true" for a frameworks section does the trick.
>>
>>
>> <frameworks root="/Foo" embed="true">
>> </frameworks>
>>
>> Uli
>> Am 07.09.2006 um 15:28 schrieb Ken Anderson:
>>
>>> Well, the combined frameworks are about 20 MB, so not so bad...
>>> we have about 10 WOApps, so a sum total of 200 MB.
>>>
>>> OK, if I go that way, is there an easy way ?
>>>
>>> Thanks,
>>> Ken
>>>
>>> On Sep 7, 2006, at 9:19 AM, Ulrich Köster wrote:
>>>
>>>> What does large mean. 10, 100 or 1000mb? I'll recommend to embed
>>>> the frameworks. Makes life much easier.
>>>>
>>>> Uli
>>>> Am 07.09.2006 um 14:58 schrieb Ken Anderson:
>>>>
>>>>> I have a situation where I want to be able to deploy multiple
>>>>> versions of frameworks on the same machine at the same time (so
>>>>> I can have multiple versions of the WOApps). At the moment, I
>>>>> install all frameworks in the typical /Library/Frameworks
>>>>> directory on the machine (an xserve running OS X).
>>>>>
>>>>> My guess is that, since we're talking jars and classpaths here,
>>>>> I could modify the classpath file generated by WOLips on install
>>>>> so that the frameworks and apps could point to a different
>>>>> location, maybe like:
>>>>>
>>>>> /Library/Commoditrack/Build316/Frameworks
>>>>> /Library/Commoditrack/Build404/Frameworks
>>>>>
>>>>> Ideally, I would like to have a special target in the Ant
>>>>> build.xml file that would figure out the subversion version
>>>>> number and use that when generating all the classpath files.
>>>>>
>>>>> Does anyone have any thoughts on this? Hints? Ideas? I'm no
>>>>> Ant expert.
>>>>>
>>>>> Our frameworks are pretty large, and we have a number of WOApps
>>>>> that use them, so I don't want to copy the jars into each
>>>>> WOApp. I would also prefer to continue using the ability for
>>>>> the EOModels to be loaded automatically from their bundles, but
>>>>> that's not 100% necessary.
>>>>>
>>>>> Thanks,
>>>>> Ken
>>>>>
>>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Thu Sep 07 2006 - 11:52:21 EDT