So this is not really the ideal solution either, it's just a shortcut
for one part of the process ... This code "guesses" that the eclipse
project name corresponds to a /Lib/Fram framework, and after that it
works like it always did. The problem is that if you build from
Eclipse, it requires that you have the /Lib/Fram version installed --
it won't build it from the Eclipse project version. A proper fix for
this problem would be for the Eclipse version to actually track
eclipse project frameworks and build them directly. If you don't
embed it's OK, but if you embed, you could get burned (though not
really any more burned than you would have been when you manually
setup the WebObjects Frameworks dialog -- just have to remember it).
ms
On Jul 18, 2007, at 8:12 AM, Mike Schrag wrote:
> Holy crap ... Denis and Lachlan, you have just rocked my world
> view. You're 100% correct, and I stand corrected :)
>
> Chuck -- They're totally right. In wolips.jdt plugin, there's an
> UpdateFrameworkIncludeFiles that runs any time .classpath changes.
> When this happens, the plugin goes through and looks for project
> dependencies that are WOLips projects and that are Frameworks, and
> automatically adds entries in ant.frameworks.wo.wolocalroot for
> Libraries/Frameworks/ThatOtherProject. 1) I have no idea how I
> never noticed this before, and 2) I want the years of my life back
> that were spent in the "WebObjects Frameworks" dialog. This code
> has existed since at least 2004.
>
> ms
>
> On Jul 17, 2007, at 7:38 PM, 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? How does the classpath to the
>> installed framework get generated?
>>
>>
>> Chuck
>>
>> --
>>
>> Practical WebObjects - for developers who want to increase their
>> overall knowledge of WebObjects or who are trying to solve
>> specific problems.
>> http://www.global-village.net/products/practical_webobjects
>>
>>
>>
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Wed Jul 18 2007 - 11:19:17 EDT