Hi Kaelin,
Am 05.12.2003 um 17:41 schrieb Kaelin Colclasure:
> Ahh, I see it now. You manipulate this using the Java Build Path
> dialog -- very nice. So, is it still necessary (for new projects) to
> use the WOLips > Add Local Framework context menu, or is just adding
> the framework via the container in the Java Build Path dialog
> sufficient? (I.e. will the framework get added to PB.project, etc. if
> I just add it via Java Build Path next time, or are both of the steps
> I took this time [WOLips > Add Local Framework then update container
> in Java Build Path] required?)
It's even possible to use the container for existing projects. 'Add
Library' does the trick. Forget the actions from the context menu
(WOLips -> Add ..... Framework) and use the container instead. Your
PB.project also reflects the changes to the container.
Ulrich
>
> -- Kaelin
> On Thursday, December 4, 2003, at 01:16 PM, Ulrich Köster wrote:
>
>> Hi Kaelin,
>>
>> you have to change the classpath manually. Remove the jars from the
>> classpath and select your local frameworks in the classpath
>> container.
>>
>> Ulrich
>>
>> Am 04.12.2003 um 21:33 schrieb Kaelin Colclasure:
>>
>>> I appreciate the streamlined appearance of the WOLips package
>>> explorer in the more recent versions, but I see that local
>>> frameworks still appear as individual jar files and are not
>>> collected under the "WO Frameworks" classpath container. Is there
>>> any way to hide them there? Or perhaps to have another "Local
>>> Frameworks" container that collects them all?
>>>
>>> -- Kaelin
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Fri Dec 05 2003 - 15:25:08 EST