Chuck is right -- Unless you have a custom ant build script, the
woproject tasks will not be able to find the frameworks to embed
unless you put them in WOFrameworks, so while it runs fine in
Eclipse, with a stock setup, you won't be able to build for deployment.
ms
On Jul 17, 2007, at 7:49 PM, Lachlan Deck wrote:
> On 18/07/2007, at 9:38 AM, Chuck Hill wrote:
>
>> On Jul 17, 2007, at 4:31 PM, Lachlan Deck wrote:
>>
>>> On 18/07/2007, at 9:25 AM, Lachlan Deck wrote:
>>>
>>>> On 18/07/2007, at 8:40 AM, Chuck Hill wrote:
>>>>
>>>>> On Jul 17, 2007, at 3:36 PM, Joshua Archer wrote:
>>>>>
>>>>>> I had added the jar to the build path in the 'Libraries' tab,
>>>>>> and the framework to the "required projects on the build path"
>>>>>> under Projects. I've removed them from the latter, and things
>>>>>> are moving along differently now...
>>>>>
>>>>> Um, no. You should check / select the framework in the
>>>>> WebObjects Frameworks library and add the project in Eclipse to
>>>>> Required Projects.
>>>>
>>>> Actually Chuck - you do one or the other; not both. They both
>>>> have the same effect (in terms of the classpath) at runtime.
>>>
>>> Sorry... I should clarify that by saying that it is not required
>>> to check/select the framework in the WebObjects Frameworks
>>> Library if you've added the framework as a project dependency.
>>> i.e., you can do both but checking it in the WebObjects
>>> Frameworks Library is optional.
>>
>> What happens when you deploy?
>
> The app runs as expected with the correct classpath ;-)
>
>> How does the classpath to the installed framework get generated?
>
> same as normal - depending also on whether you've set the embedding
> option in your ant build file or not.
>
> with regards,
> --
>
> Lachlan Deck
This archive was generated by hypermail 2.0.0 : Tue Jul 17 2007 - 20:44:20 EDT