I'm actually RUNNING on 3.2M6 at the moment without any noticeable
issues, but I'm a few wolips versions back now (I think I'm running
the versions JUST PRIOR to your (Sebastien's) set of checkins (no
offense, just been lazy :) ). I was going to upgrade to the latest
when I ran into that build problem with XcodeProject, so maybe I'll
try to upgrade again later tonight when I get home and see how it goes.
ms
On Apr 18, 2006, at 12:48 PM, Sébastien Sahuc wrote:
> Anjo, Mikes,
>
> What is the status on using Eclipse 3.2M6 with respect to the
> required plugins ? Can you report what is broken ?
>
> Thanks,
>
> Sebastien
>
> On Apr 18, 2006, at 9:25 AM, Anjo Krank wrote:
>
>> I'm not sure what you mean? The startup time of the app or of
>> Eclipse itself? I haven't noticed any startup problems with
>> regards to the app and Eclipse I start up about once a month or so.
>>
>> Send me your patch and I'll take a look, but I can't promise
>> anything as M6 isn't working for me and I had other problems with
>> the head when I downgrade.
>>
>> Cheers, Anjo
>>
>>
>> Am 18.04.2006 um 17:00 schrieb Watkins, Garry:
>>
>>> I think this is an unacceptable solution because of the startup
>>> time with
>>> eclipse having multiple projects open.
>>>
>>> I have modified the WORuntimeClasspathProvider class to support a
>>> mixed
>>> environment (Project Frameworks and Binary Frameworks) can
>>> coexist. I have
>>> been running it for about a month now and I think that it is stable.
>>>
>>> What is the process for me to submit this?
>>>
>>> I am also looking at fixing the PB.project generation so that it
>>> will not
>>> list the same frameworks (if there is more than one jar) and
>>> components more
>>> than once. If someone can tell me where to start, I would gladly
>>> take a
>>> look at it.
>>>
>>> Thanks
>>> Garry
>>>
>>>
>>>
>>> On 4/18/06 2:14 AM, "Anjo Krank" <kran..ogicunited.com> wrote:
>>>
>>>> The best way to debug under Eclipse is to *either* build everything
>>>> seperately and link only binary frameworks *or* to include
>>>> everything
>>>> as projects. I recently fixed Project Wonder to do the latter.
>>>>
>>>> If you need to test your app with the custom-built framework
>>>> jar, do
>>>> so in the shell.
>>>>
>>>> Am 13.04.2006 um 18:55 schrieb Sébastien Sahuc:
>>>>
>>>>> I'm actually surprised it is 'bin' where I expected a 'build' as
>>>>> in : Users/pierre/Projects/workspace/SurveyCreation/BUILD/
>>>>> SurveyCreation.woa
>>>>>
>>>>> Which version of WOLips are you using ?
>>>>>
>>>>> And to answer your question, you shouldn't need to run the app
>>>>> from
>>>>> ~/Roots if all frameworks are properly added to the classpath. I
>>>>> would suggest you explicitely add the jars that get moved by your
>>>>> build.xml into you /Library/Java/Extensions into your project
>>>>> classpath within eclipse. At least you'll know for sure if those
>>>>> are missing when running within eclipse.
>>>>>
>>>>> Sebastien
>>>>>
>>>>> On Apr 13, 2006, at 9:45 AM, Pierre Frisch wrote:
>>>>>
>>>>>> Users/pierre/Projects/workspace/SurveyCreation/bin/
>>>>>> SurveyCreation.woa
>>>>>
>>>>
>>>
>>> --
>>> Garry Watkins
>>>
>>> Database Administrator
>>> Motley Rice LLC
>>> 843-216-9639
>>>
>>>
>>>
>>>
>>>
>>>
>>> Confidential & Privileged
>>>
>>> Unless otherwise indicated or obvious from its nature, the
>>> information contained in this communication is attorney-client
>>> privileged and confidential information/work product. This
>>> communication is intended for the use of the individual or entity
>>> named above. If the reader of this communication is not the
>>> intended recipient, you are hereby notified that any
>>> dissemination, distribution or copying of this communication is
>>> strictly prohibited. If you have received this communication in
>>> error or are not sure whether it is privileged, please
>>> immediately notify us by return e-mail and destroy any copies--
>>> electronic, paper or otherwise--which you may have of this
>>> communication.
>>>
>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Tue Apr 18 2006 - 13:09:08 EDT