out of the box.
>
> Parag Chandra
> Senior Software Developer
> [EMAIL PROTECTED]
> 404-439-5821
>
> -Original Message-
> From: Markus Sinner [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 25, 2008 2:01 AM
> To: eclipseme-users@lists.sourceforge.net
>
, June 25, 2008 2:01 AM
To: eclipseme-users@lists.sourceforge.net
Subject: Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and
EclipseME 1.7.9 [SOLVED]
> Hi all,
>
> I finally figured out why things weren't working as expected. The debug
> mode of EclipseME helped m
>> 404-439-5821
>> -Original Message-
>> From: Berk Birand [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, June 24, 2008 6:46 AM
>> To: eclipseme-users@lists.sourceforge.net
>> Subject: Re: [Eclipseme-users] ClassNotFound problem with Eclipse
>> 3.3 and E
> Hi all,
>
> I finally figured out why things weren't working as expected. The debug
> mode of EclipseME helped me a lot. It turns out my first mistake was in
> deleting the content of the .eclipseme.tmp directory, including the
> emulator/ and verified/ directories. I thought those would be
riginal Message-
> From: Berk Birand [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 24, 2008 6:46 AM
> To: eclipseme-users@lists.sourceforge.net
> Subject: Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and
> EclipseME 1.7.9 [SOLVED]
>
> Hi all,
>
>
ator. But then you always
>> have to create the package explicitly after modifying the sources.
>>
>> Heiko
>
>
>>
>> Original-Nachricht
>>> Datum: Tue, 24 Jun 2008 00:39:24 +0200
>>> Von: Markus Sinner <[EMAIL PROTECTED]>
&
>> have to create the package explicitly after modifying the sources.
>>
>> Heiko
>
>
>>
>> ---- Original-Nachricht
>>> Datum: Tue, 24 Jun 2008 00:39:24 +0200
>>> Von: Markus Sinner <[EMAIL PROTECTED]>
>>> An: eclipsem
ner <[EMAIL PROTECTED]>
>> An: eclipseme-users@lists.sourceforge.net
>> Betreff: Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and
>> EclipseME 1.7.9
>
>> You should open a bug report on sourceforge if it persists...
>>
>> Did you run yo
I'm not sure what is going on, but I can say that messing with the
classpath probably isn't going to solve the problem. Have you done a
project Clean operation? The information on the builder logging can
be found in the EclipseME documentation at
http://eclipseme.org/docs/buildingRef.html
9:24 +0200
> Von: Markus Sinner <[EMAIL PROTECTED]>
> An: eclipseme-users@lists.sourceforge.net
> Betreff: Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and
> EclipseME 1.7.9
> You should open a bug report on sourceforge if it persists...
>
> Did you run
You should open a bug report on sourceforge if it persists...
Did you run your midlet "over the air"? Try specifying the midlet in the
run-tab, if I remember right it is the third option.
Berk Birand schrieb:
> Hi all,
>
> I am developing my first MIDlet using Eclipse 3.3 and EclipseME 1.7.9.
>
Hi all,
I am developing my first MIDlet using Eclipse 3.3 and EclipseME 1.7.9.
The development started fairly smoothly, and I managed to run the
important demos in the Sun WTK 2.5.2, I recently ran into some weird
problems that no amount of Googling could solve. It all began when I
made a lot
12 matches
Mail list logo
