eclipseme-users — This mailing list is for public discussion of the users of EclipseME.

Re: [Eclipseme-users] Controlling which midlet to run in a Midlet Suite

[Russel W. <ru...@ru...>]

On Thu, 2008-08-21 at 02:53 -0700, Jimisola Laursen wrote:
> Hi!
> 
> Using Eclipse 3.4 with EclipseME 1.8.0 and SonyEricsson J2ME SDK 2.5.0.2.

I must be missing something, isn't 1.7.9 the latest release of
EclipseME ?

-- 
Russel.
====================================================
Dr Russel Winder                       t: +44 20 7585 2200
41 Buckmaster Road               m: +44 7770 465 077
London SW11 1EN, UK              w: http://www.russel.org.uk/

[Eclipseme-users] Controlling which midlet to run in a Midlet Suite

[Jimisola L. <jim...@ji...>]

Hi!

Using Eclipse 3.4 with EclipseME 1.8.0 and SonyEricsson J2ME SDK 2.5.0.2.

I have a midlet suite that contains my self-developed midlet (call it
MyMidlet) and a midlet (RecordStoreLogViewer) that comes with the J2ME-log4j
look-alike MicroLog. That is, both midlets are added to the Midlet tab in
the Application Description Editor (aka JAD file).

When I run/debug using Debug-On-Device the RecordStoreLogViewer comes up and
not MyMidlet!
However, if I run/debug using the Emulator MyMidlet runs correctly.

I've checked the Run Configuration for the Midlet and Midlet -> Executable
has the full classname of MyMidlet.

Do I need to specify which Midlet to run per default in the JAD file?
Is this a bug in the SDK or perhaps in EclipseME?

Console output:

Creating classpackager: {MIDlet-Jar-Size=119395, MIDlet-2=Log
Viewer,,net.sf.microlog.ui.RecordStoreLogViewer,
MIDlet-1=MyMidlet,,net.midlet.MyMidlet, MIDlet-Jar-URL=MyMidlet.jar,
MicroEdition-Configuration=CLDC-1.1, MIDlet-Version=0.8.1,
MIDlet-Name=MyMidlet Midlet Suite, MIDlet-Description=My Midlet,
MIDlet-Vendor=Midlet Suite Vendor, MicroEdition-Profile=MIDP-2.0}

Regards,
Jimisola

-- 
View this message in context: http://n2.nabble.com/Controlling-which-midlet-to-run-in-a-Midlet-Suite-tp737872p737872.html
Sent from the EclipseME mailing list archive at Nabble.com.

Re: [Eclipseme-users] Problem Eclipse 3.4 and J2Me

[J. S. <j.s...@gm...>]

Thanks Craig,

This helped me alot. For some reason my project didnt have the second JAD file in the root folder so I was constantly changing the values in the one that is used to execute the midlet. Thanks for this little tip. Now I can continue developing the app :)

Setera Craig schreef:
> You said...
> 
>> Now I dont understand what is going wrong here. There is one strange
>> thing about the JAD file. Everytime I recreate the package the JAD  
>> file
>> is reset to only a 2 line file containing only the midlet jar url and
>> the size . All the other things are left out.
> 
> 
> It may not be completely clear (ok, it is just plain confusing  
> <grin>)  There are two JAD files in every EclipseME project.  The JAD  
> file at the top-level is the one that should be altered by the  
> developer.. The other is the one that the system uses for launching  
> and should not be altered by hand.  Are you sure you are editing the  
> correct JAD file?
> 
> Also, there are some known issues with the most recent official  
> release of EclipseME on Eclipse 3.4.  Please give the version at http://eclipseme.org/testversions 
>   a try and see if it helps you out.  I've had very little "play" time  
> recently and I've spent a bit more time working on the EclipseME to  
> MTJ porting work.  The good news is that we are making some progress  
> there.
> 
> Hope that helps,
> Craig
> 
> On Aug 3, 2008, at 3:29 PM, J. Somhorst wrote:
> 
>> Hello Everyone,
>>
>> After a few days of hard work on my latest J2Me project I decided it
>> would be the time to test it on my own HTC P3300 phone. So I created  
>> the
>> package and uploaded it to my phone.
>>
>> When I tried to install it the phone gave me an error saying that it
>> could be intalled. I had this issue already a few months ago so i
>> changed the mirocedition configuration and profile in the jad file,
>> repackaged again and uploaded it. Still an error.
>>
>> Now I dont understand what is going wrong here. There is one strange
>> thing about the JAD file. Everytime I recreate the package the JAD  
>> file
>> is reset to only a 2 line file containing only the midlet jar url and
>> the size . All the other things are left out.
>>
>> Does anyone know what to do next ?
>>
>> (p.s. the HTC P3300 only accepts Midlets packaged with MIDP 2.0 and  
>> CLDC
>>  1.1 )
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 

Re: [Eclipseme-users] Problem Eclipse 3.4 and J2Me

[Setera C. <cra...@se...>]

You said...

> Now I dont understand what is going wrong here. There is one strange
> thing about the JAD file. Everytime I recreate the package the JAD  
> file
> is reset to only a 2 line file containing only the midlet jar url and
> the size . All the other things are left out.


It may not be completely clear (ok, it is just plain confusing  
<grin>)  There are two JAD files in every EclipseME project.  The JAD  
file at the top-level is the one that should be altered by the  
developer.. The other is the one that the system uses for launching  
and should not be altered by hand.  Are you sure you are editing the  
correct JAD file?

Also, there are some known issues with the most recent official  
release of EclipseME on Eclipse 3.4.  Please give the version at http://eclipseme.org/testversions 
  a try and see if it helps you out.  I've had very little "play" time  
recently and I've spent a bit more time working on the EclipseME to  
MTJ porting work.  The good news is that we are making some progress  
there.

Hope that helps,
Craig

On Aug 3, 2008, at 3:29 PM, J. Somhorst wrote:

> Hello Everyone,
>
> After a few days of hard work on my latest J2Me project I decided it
> would be the time to test it on my own HTC P3300 phone. So I created  
> the
> package and uploaded it to my phone.
>
> When I tried to install it the phone gave me an error saying that it
> could be intalled. I had this issue already a few months ago so i
> changed the mirocedition configuration and profile in the jad file,
> repackaged again and uploaded it. Still an error.
>
> Now I dont understand what is going wrong here. There is one strange
> thing about the JAD file. Everytime I recreate the package the JAD  
> file
> is reset to only a 2 line file containing only the midlet jar url and
> the size . All the other things are left out.
>
> Does anyone know what to do next ?
>
> (p.s. the HTC P3300 only accepts Midlets packaged with MIDP 2.0 and  
> CLDC
>  1.1 )
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's  
> challenge
> Build the coolest Linux based applications with Moblin SDK & win  
> great prizes
> Grand prize is a trip for two to an Open Source event anywhere in  
> the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users

[Eclipseme-users] Problem Eclipse 3.4 and J2Me

[J. S. <j.s...@gm...>]

Hello Everyone,

After a few days of hard work on my latest J2Me project I decided it 
would be the time to test it on my own HTC P3300 phone. So I created the 
package and uploaded it to my phone.

When I tried to install it the phone gave me an error saying that it 
could be intalled. I had this issue already a few months ago so i 
changed the mirocedition configuration and profile in the jad file, 
repackaged again and uploaded it. Still an error.

Now I dont understand what is going wrong here. There is one strange 
thing about the JAD file. Everytime I recreate the package the JAD file 
is reset to only a 2 line file containing only the midlet jar url and 
the size . All the other things are left out.

Does anyone know what to do next ?

(p.s. the HTC P3300 only accepts Midlets packaged with MIDP 2.0 and CLDC 
  1.1 )

Re: [Eclipseme-users] create package failed running preverification

[Craig S. <cra...@se...>]

Glad to hear it.

ecl...@ek... wrote:
> Hi,
>
> I added the url to the software updates list, and upgraded to 1.8. Works fine 
> now.
>
> Thanks.
>
> On Tuesday 22 July 2008 03:28:38 Craig Setera wrote:
>   
>> I believe this is a known issue on Eclipse 3.4.  Please try the version
>> at http://eclipseme.org/testversions and see if it resolves your problem.
>>
>> Thanks,
>> Craig
>>
>> ecl...@ek... wrote:
>>     
>>> Hi,
>>>
>>> I am trying to build and run the lwuitdemo.
>>>
>>> The project compiles, I can see .class files in projects bin directory,
>>> but when I select J2ME->'Create Package' from the project, I get an
>>> error:
>>>
>>> Errors runing builder 'Preverification' on project '...'
>>> org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resour
>>> ces/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
>>> org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resour
>>> ces/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
>>>
>>> I am using eclpse 3.4; eclipseme 1.7.9; Sun Wireless Toolkit 2.5.2. I
>>> turned on extra logging, and attached output for the 'Create Package'
>>> action.
>>>       
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>   

Re: [Eclipseme-users] create package failed running preverification

[<ecl...@ek...>]

Hi,

I added the url to the software updates list, and upgraded to 1.8. Works fine 
now.

Thanks.

On Tuesday 22 July 2008 03:28:38 Craig Setera wrote:
> I believe this is a known issue on Eclipse 3.4.  Please try the version
> at http://eclipseme.org/testversions and see if it resolves your problem.
>
> Thanks,
> Craig
>
> ecl...@ek... wrote:
> > Hi,
> >
> > I am trying to build and run the lwuitdemo.
> >
> > The project compiles, I can see .class files in projects bin directory,
> > but when I select J2ME->'Create Package' from the project, I get an
> > error:
> >
> > Errors runing builder 'Preverification' on project '...'
> > org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resour
> >ces/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
> > org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resour
> >ces/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
> >
> > I am using eclpse 3.4; eclipseme 1.7.9; Sun Wireless Toolkit 2.5.2. I
> > turned on extra logging, and attached output for the 'Create Package'
> > action.

Re: [Eclipseme-users] create package failed running preverification

[<ecl...@ek...>]

Thanks, I'll try that.

How do I install the version in testversions? Do I need to point the eclipse 
software update at the url below? Should I replace the existing ecliseme 
entry?

regards,
jeremy

On Tuesday 22 July 2008 03:28:38 Craig Setera wrote:
> I believe this is a known issue on Eclipse 3.4.  Please try the version
> at http://eclipseme.org/testversions and see if it resolves your problem.
>
> Thanks,
> Craig
>
> ecl...@ek... wrote:
> > Hi,
> >
> > I am trying to build and run the lwuitdemo.
> >
> > The project compiles, I can see .class files in projects bin directory,
> > but when I select J2ME->'Create Package' from the project, I get an
> > error:
> >
> > Errors runing builder 'Preverification' on project '...'
> > org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resour
> >ces/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
> > org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resour
> >ces/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
> >
> > I am using eclpse 3.4; eclipseme 1.7.9; Sun Wireless Toolkit 2.5.2. I
> > turned on extra logging, and attached output for the 'Create Package'
> > action.

Re: [Eclipseme-users] Configuring preprocessor support ?

[Craig S. <cra...@se...>]

Eclipse 3.4 does not provide the necessary support, so it is still 
necessary to go through the installation steps listed to get 
preprocessing working.

María Amor Vázquez wrote:
> Hi all,
>
> I was following the steps to install EclipseME and a question came up. I 
> have a recent version of Eclipse (3.4.0), does it still have the bug 
> that's mentioned in the EclipseMe installation steps? I mean, do I have 
> to do the steps to fix this bug (i am talking about the section 
> "configuring preprocessor support")
> The versions I have are: J2SE 1.5.0_16, Eclipse 3.4.0, WTK 2.5.2 and 
> EclipseMe 1.7.9
>
> Thanks a lot in advance
> Best regards,
> María Amor
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>   

Re: [Eclipseme-users] create package failed running preverification

[Craig S. <cra...@se...>]

I believe this is a known issue on Eclipse 3.4.  Please try the version 
at http://eclipseme.org/testversions and see if it resolves your problem.

Thanks,
Craig

ecl...@ek... wrote:
> Hi,
>
> I am trying to build and run the lwuitdemo.
>
> The project compiles, I can see .class files in projects bin directory, but 
> when I select J2ME->'Create Package' from the project, I get an error:
>
> Errors runing builder 'Preverification' on project '...'
> org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resources/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
> org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resources/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
>
> I am using eclpse 3.4; eclipseme 1.7.9; Sun Wireless Toolkit 2.5.2. I turned 
> on extra logging, and attached output for the 'Create Package' action.
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users

[Eclipseme-users] create package failed running preverification

[<ecl...@ek...>]

Hi,

I am trying to build and run the lwuitdemo.

The project compiles, I can see .class files in projects bin directory, but 
when I select J2ME->'Create Package' from the project, I get an error:

Errors runing builder 'Preverification' on project '...'
org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resources/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;
org.eclipse.jdt.internal.core.JvaModel.getTarget(Lorg/eclipse/core/resources/IContainer;Lorg/eclipse/core/runtime/IPath;Z)Ljava/lang/Object;

I am using eclpse 3.4; eclipseme 1.7.9; Sun Wireless Toolkit 2.5.2. I turned 
on extra logging, and attached output for the 'Create Package' action.

[Eclipseme-users] Configuring preprocessor support ?

[María A. V. <ma...@tr...>]

Hi all,

I was following the steps to install EclipseME and a question came up. I 
have a recent version of Eclipse (3.4.0), does it still have the bug 
that's mentioned in the EclipseMe installation steps? I mean, do I have 
to do the steps to fix this bug (i am talking about the section 
"configuring preprocessor support")
The versions I have are: J2SE 1.5.0_16, Eclipse 3.4.0, WTK 2.5.2 and 
EclipseMe 1.7.9

Thanks a lot in advance
Best regards,
María Amor

Re: [Eclipseme-users] Issue with exporting Antenna files from Eclipse and project dependencies

[Rory F. <ba...@go...>]

Sorry to dig up an old thread but I'm coming accross the same problem and
was wondering if theres been any progress in diagnosing it? I considered
looking at it myself but realised it would take forever just to know where
to look!

I have several projects depending on each other but even one with only one
dependency fails with the same error as below.

I'm running:
Eclipse 3.3.1.1
EclipseME 1.7.9
Antenna 1.1.0-beta (I think)

Is the MJT platform in a state that we can start moving accross to it?
(slightly unrelated, just thought I'd ask!)

Cheers
Rory

Scott,

I will have to look at this a bit more closely when I have more time and
brain power. You may have found a problem with the export, but my brain
is not functioning well enough at this point in the day to sort it out. :-)

Thanks,
Craig

Williams, Scott wrote:
> I am trying to configure my Eclipse J2ME projects such that I can do
> command line builds. I can build and run the emulator from Eclipse, but
> I cannot build with the generated Antenna Build files. The issue seems
> be when one project is a dependency of the other. I was able to come up
> with a workaround by modifying the eclipseme-build.xml file, but I'm
> looking for a better solution.
>
> Here's what I did:
> - Create a TestLib J2ME Suite
> - Put a single Java class called TestClass in a package called com.foo.
> It's constructor does a System.out.println() so I can tell when it's
> called
> - Create a TestApp J2ME Suite
> - Put a single Midlet class whose startApp() also does a
> System.out.println(), then creates an instance of com.foo.TestClass
> - Add TestLib to the Java Build Path of TestApp, and have it checked in
> the Order and Export tab.
>
> When I run this from within Eclipse, the Emulator starts and I see both
> of my print messages and everything seems happy.
>
> Then I started trying to work on getting things working from the command
> line. First I export the Antenna build files for the TestLib library
> and built that. Then I export the Antenna build files for the main
> TestApp application, try to build that, and get this error:
> ===================================================
> C:\Documents and Settings\swilliams\workspace\TestApp>%ANT_HOME%\bin\ant
> Buildfile: build.xml
>
> -initialize:
> [echo] Initializing build environment...
>
> -eclipseme-initialize:
> [echo] Initializing EclipseME Antenna build environment...
>
> -eclipseme-build:
> [echo] Building source files...
> [wtkbuild]
> **************************************************************
> [wtkbuild] * Antenna 0.9.15 initialized for project "TestApp"
> *
> [wtkbuild] * Using Sun Wireless Toolkit 2.5 (CLDC-1.1; MIDP-2.1)
> *
> [wtkbuild]
> **************************************************************
> [wtkbuild] Compiling 1 source file to C:\Documents and
> Settings\swilliams\workspace\TestApp\9db49ca5.tmp\tmpclasses
> [wtkbuild] C:\Documents and
> Settings\swilliams\workspace\TestApp\src\TestMidlet.java:23: package
> com.foo does not exist
> [wtkbuild] new com.foo.TestClass();
> [wtkbuild] ^
> [wtkbuild] 1 error
>
> BUILD FAILED
> C:\Documents and
> Settings\swilliams\workspace\TestApp\eclipseme-build.xml:25: Compile
> failed; see the compiler error output for details.
> ===================================================
>
> I came up with a workaround by changing three things in
> eclipseme-build.xml:
>
> I changed the locations of classpath.TestLib (they were oddly the same
> as classpath.TestApp? Is this right?) I changed this:
> <path id="classpath.TestLib">
> <path location="${path.build.classes}"/>
> <path location="${path.build.classes}/_no_export"/>
> </path>
> To this:
> <path id="classpath.TestLib">
> <path location="${project.root.TestLib}/build/classes"/>
> <path
> location="${project.root.TestLib}/build/classes/_no_export"/>
> </path>
>
> And then I changed the classpath being used in the -eclipseme-build
> target to refer to classpath.TestLib instead of classpath.TestLib. I
> changed this:
> <target depends="-eclipseme-initialize" name="-eclipseme-build">
> <echo message="Building source files..."/>
> <wtkbuild destdir="${path.build.classes}"
> encoding="${src.encoding}" source="1.3" sourcepath=""
> srcdir="${project.root.TestApp}/src">
> <classpath refid="classpath.TestApp"/>
> </wtkbuild>
> <wtkbuild destdir="${path.build.classes}"
> encoding="${src.encoding}" source="1.3" sourcepath=""
> srcdir="${project.root.TestApp}/res">
> <classpath refid="classpath.TestApp"/>
> </wtkbuild>
> </target>
> To this:
> <target depends="-eclipseme-initialize" name="-eclipseme-build">
> <echo message="Building source files..."/>
> <wtkbuild destdir="${path.build.classes}"
> encoding="${src.encoding}" source="1.3" sourcepath=""
> srcdir="${project.root.TestApp}/src">
> <classpath refid="classpath.TestLib"/>
> </wtkbuild>
> <wtkbuild destdir="${path.build.classes}"
> encoding="${src.encoding}" source="1.3" sourcepath=""
> srcdir="${project.root.TestApp}/res">
> <classpath refid="classpath.TestLib"/>
> </wtkbuild>
> </target>
>
> And then in the -eclipseme-internal-package task I changed the
> classpath.TestLib to be a libclasspath instead of a classpath so it
> would be included in the final jar. I changed this:
> <target depends="-eclipseme-build"
> name="-eclipseme-internal-package">
> <copy file="${midlet.name}.jad" todir="${path.build.output}"/>
> <wtkpackage autoversion="${flag.autoversion}"
> jadfile="${path.build.output}/${midlet.name}.jad"
> jarfile="${path.build.output}/${midlet.name}.jar" obfuscate="false"
> preverify="${flag.preverify}">
> <fileset dir="${path.build.classes}">
> <exclude name="_no_export/"/>
> </fileset>
> <classpath refid="classpath.TestApp"/>
> <fileset dir="${project.root.TestApp}/src">
> <exclude name="**/*.java"/>
> <exclude name="build/"/>
> </fileset>
> <fileset dir="${project.root.TestApp}/res">
> <exclude name="**/*.java"/>
> <exclude name="build/"/>
> </fileset>
> <classpath refid="classpath.TestLib"/>
> </wtkpackage>
> <antcall target="-eclipseme-obfuscate"/>
> </target>
> To this:
> <target depends="-eclipseme-build"
> name="-eclipseme-internal-package">
> <copy file="${midlet.name}.jad" todir="${path.build.output}"/>
> <wtkpackage autoversion="${flag.autoversion}"
> jadfile="${path.build.output}/${midlet.name}.jad"
> jarfile="${path.build.output}/${midlet.name}.jar" obfuscate="false"
> preverify="${flag.preverify}">
> <fileset dir="${path.build.classes}">
> <exclude name="_no_export/"/>
> </fileset>
> <classpath refid="classpath.TestApp"/>
> <fileset dir="${project.root.TestApp}/src">
> <exclude name="**/*.java"/>
> <exclude name="build/"/>
> </fileset>
> <fileset dir="${project.root.TestApp}/res">
> <exclude name="**/*.java"/>
> <exclude name="build/"/>
> </fileset>
> <libclasspath refid="classpath.TestLib"/>
> </wtkpackage>
> <antcall target="-eclipseme-obfuscate"/>
> </target>
>
> And then everything built, and I can run the emulator from the command
> line and it printed out both messages.
>
> So I don't really want to modify eclipseme-build.xml; so my questions
> are did I figure my project(s) wrong, or did I uncover a bug in how
> eclipseme-build.xml is being generated? And, if so, is there a
> different/better way for me to work around the issue than to change the
> eclipseme-build.xml file?
>
> Here's my configuration:
> Eclipse: Version: 3.3.2 (Build id: M20080221-1800)
> Antenna 1.0.0 (although it seems to report itself as 0.9.15)
> Eclipse ME 1.7.7
> Wireless Toolkit 2.5.2
> Ant 1.7.0
>
> Thanks.
>
> ---
> Scott Williams
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Eclipseme-users mailing list
> Eclipseme-users@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[Craig S. <cra...@se...>]

Parag,

You are seeing some of the Smalltalk-based heritage of the Eclipse 
tooling with the refresh necessity.  For those of us that grew up 
through those tools, this isn't so hard to deal with, although it is 
annoying at times.  I think they will likely try to better address some 
of this with the new "e4" effort that has begun for defining the next 
generation of Eclipse tooling.

Craig

PAR...@OR... wrote:
> I wonder if enabling this option:
>
> Window...Preferences...General...Workspace...Refresh automatically
>
> would let EclipseME know that the directory had been deleted? Until I discovered this option last week, my biggest complaint about Eclipse vs. Visual Studio was that the entire Package Explorer had to be manually refreshed any time you made changes outside of Eclipse. I feel like this option should be enabled out of the box.
>
> Parag Chandra
> Senior Software Developer
> par...@or...
> 404-439-5821
>
> -----Original Message-----
> From: Markus Sinner [mailto:si...@ps...] 
> Sent: Wednesday, June 25, 2008 2:01 AM
> To: ecl...@li...
> 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 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 
>> regenerated the next round, but I suppose that wasn't the case, since I 
>> kept seeing FileNotFound exceptions in the EclipseME console.
>>     
> That kind of problems always occur in eclipse if you delete folders NOT
> using eclipse. If you go to resource view, update it (F5) and then try
> again, it should work, because then eclipse "knows" about the current
> filesystem. If not, I suggest opening a bugreport.
>
> Thats very annoying about eclipse.
>
>   
>> I apologize for making a novice mistake like this, but I am indeed a 
>> beginner and have been developing for this platform for about 3 days. On 
>> the flip side, I learned a lot about writing programs for this platform, 
>> and I hopefully won't be wasting your time with inconsequential problems 
>> (I'll be wasting it with more difficult ones).
>>     
> I think all of us had similar problems :-)
>
>
>   

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[<PAR...@OR...>]

I wonder if enabling this option:

Window...Preferences...General...Workspace...Refresh automatically

would let EclipseME know that the directory had been deleted? Until I discovered this option last week, my biggest complaint about Eclipse vs. Visual Studio was that the entire Package Explorer had to be manually refreshed any time you made changes outside of Eclipse. I feel like this option should be enabled out of the box.

Parag Chandra
Senior Software Developer
par...@or...
404-439-5821

-----Original Message-----
From: Markus Sinner [mailto:si...@ps...] 
Sent: Wednesday, June 25, 2008 2:01 AM
To: ecl...@li...
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 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 
> regenerated the next round, but I suppose that wasn't the case, since I 
> kept seeing FileNotFound exceptions in the EclipseME console.
That kind of problems always occur in eclipse if you delete folders NOT
using eclipse. If you go to resource view, update it (F5) and then try
again, it should work, because then eclipse "knows" about the current
filesystem. If not, I suggest opening a bugreport.

Thats very annoying about eclipse.

> I apologize for making a novice mistake like this, but I am indeed a 
> beginner and have been developing for this platform for about 3 days. On 
> the flip side, I learned a lot about writing programs for this platform, 
> and I hopefully won't be wasting your time with inconsequential problems 
> (I'll be wasting it with more difficult ones).
I think all of us had similar problems :-)


-- 

*********************************
si...@ps...
http://www.psitronic.de

psitronic IT-Solutions
Markus Sinner
W-Rathenau-Str. 14 - 68642 Bürstadt
Tel.: (+49)6206 / 963513
Fax:  (+49)6206 / 963514

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Eclipseme-users mailing list
Ecl...@li...
https://lists.sourceforge.net/lists/listinfo/eclipseme-users

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[Setera C. <cra...@se...>]

Berk,

It sounds like you had an interesting combination of issues.  If  
EclipseME was working correctly, you should have received an error  
marker in the Java editor.  Any chance that you had it and didn't  
notice?  If not, there is likely a bug in EclipseME which definitely  
made things more difficult for you to narrow down your problem.

I'm glad that you came to the mailing list and that you eventually  
figured out your problem.  Please feel free to create a bug report on  
Sourceforge for anything that seemed to be wrong in EclipseME.  While  
it is unclear how many bugs I will fix directly in EclipseME, I will  
make sure to work with everyone on the MTJ project to make sure that  
these bugs are fixed in the MTJ code.

Thanks,
Craig

On Jun 24, 2008, at 8:35 AM, Berk Birand wrote:

> PAR...@OR... wrote:
>> Berk, final methods are allowed in MIDP. In fact, it's one of the  
>> tricks you can use to save a few bytes in the final obfuscated JAR  
>> file. I can't say I understand why removing the final method fixed  
>> the problems you were seeing, but try adding another final method  
>> and see if it works now.
>>
> You are absolutely right, it turns out it is the "finalize" method  
> that
> is not allowed. I had it declared the method as "final finalized,"  
> and I
> guess I didn't read the error message properly. Initially I was hoping
> to put some code in there that would right my data structure to the  
> RMS
> when my model class was destroyed. It got fixed when I removed the  
> class
> altogether. Thanks for pointing that out!
>
>
>> Parag Chandra
>> Senior Software Developer
>> par...@or...
>> 404-439-5821
>> -----Original Message-----
>> From: Berk Birand [mailto:ber...@su...]
>> Sent: Tuesday, June 24, 2008 6:46 AM
>> To: ecl...@li...
>> 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 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
>> regenerated the next round, but I suppose that wasn't the case,  
>> since I
>> kept seeing FileNotFound exceptions in the EclipseME console.
>>
>> After that was done, the content of the folders were created as
>> expected, but I still got the ClassNotFound exception. Looking at the
>> preverifier output, I realized that was because I had a method  
>> declared
>> as "final," which apparently is not allowed in MIDP. Once I took that
>> out, the classes were preverified, and the emulator ran normally.
>>
>> I apologize for making a novice mistake like this, but I am indeed a
>> beginner and have been developing for this platform for about 3  
>> days. On
>> the flip side, I learned a lot about writing programs for this  
>> platform,
>> and I hopefully won't be wasting your time with inconsequential  
>> problems
>> (I'll be wasting it with more difficult ones).
>>
>> Thanks to everyone who have answered,
>> Sincerely,
>>  Berk
>>
>> Berk Birand wrote:
>>
>>> First of all, thanks a lot for all your quick answers. This has been
>>> really bugging me, and it is somewhat nice to hear that the solution
>>> doesn't stem from me having something configured improperly.
>>>
>>> After learning about the .eclipseme.tmp directory, I made some more
>>> observations that might be of help. I removed the content of the / 
>>> bin
>>> directory, and the .eclipseme.tmp directories, as explained in
>>> http://eclipseme.org/docs/buildingRef.html . I then opened  
>>> Eclipse, and
>>> attempted to re-build the project, getting the same  
>>> ClassPathNotFound
>>> exception. However when I then check in those directories, I don't  
>>> see
>>> any new .class files, so nothing appears to have been compiled.  
>>> There is
>>> a .jar file in the /emulation subfolder, but it only contains a
>>> MANIFEST.MF file.
>>>
>>> In short, the reason why it cannot find the class is because the  
>>> sources
>>> are never compiled, not because they are unreachable.
>>>
>>> Does anybody know why EclipseME would refuse to compile the  
>>> project? How
>>>  can I force it to do that? Or is there any way to diagnose why it  
>>> is
>>> not doing so?
>>>
>>>
>>> I enabled the EclipseME debug mode by using the command-line  
>>> switch, but
>>> the EclipseME error console only displays this:
>>>
>>>> PreverificationBuilder.getRuntimeJar project = P/GroceryList
>>> < PreverificationBuilder.getRuntimeJar project = P/GroceryList
>>>
>>> Thank you in advance,
>>>  Berk
>>>
>>>
>>> Heiko Selber wrote:
>>>
>>>> BTW: Putting /bin into the classpath shouldn't help anyway,  
>>>> because MIDlets must be preverified. So, if anyting, you should  
>>>> add /verified, not /bin.
>>>>
>>>> As to the original problem: For some reason, over the air doesn't  
>>>> always work for me (perhaps because of missing write permissions).
>>>>
>>>> But when I do J2ME -> Create Package and specify the MIDlet  
>>>> explicitly in the launch configuration, I can run it in the  
>>>> emulator. 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 <si...@ps...>
>>>>> An: ecl...@li...
>>>>> 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 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.
>>>>>> 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 of changes to the source code of my own application,  
>>>>>> and
>>>>>> wanted to see how it worked in the emulator. When I ran the  
>>>>>> project,
>>>>>> none of the changes showed up, and I would still see some  
>>>>>> sysout prints
>>>>>> that I had removed long ago. I then went into the Eclipse  
>>>>>> workspace, and
>>>>>> removed the content of the /bin directory, thinking that it would
>>>>>> recompile everything from the source.
>>>>>>
>>>>>> Instead, I started running into these errors:
>>>>>>
>>>>>> Running with storage root
>>>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>>>> Running with locale: en_US.UTF-8
>>>>>> Running in the untrusted security domain
>>>>>> java.lang.ClassNotFoundException: org/berk/GroceryList
>>>>>>    at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>>>>>>    at com.sun.midp.midlet.Scheduler.schedule(+52)
>>>>>>    at com.sun.midp.main.Main.runLocalClass(+28)
>>>>>>    at com.sun.midp.main.Main.main(+80)
>>>>>> Execution completed.
>>>>>> 2755738 bytecodes executed
>>>>>> 40 thread switches
>>>>>> 1665 classes in the system (including system classes)
>>>>>> 14243 dynamic objects allocated (437872 bytes)
>>>>>> 1 garbage collections (0 bytes collected)
>>>>>>
>>>>>> Somebody else had a similar problem, and they proposed  
>>>>>> including the
>>>>>> /bin directory as an "Extra Emulator Parameter" using the -cp  
>>>>>> switch.
>>>>>> When I do, the emulator does manage to find the class, but I  
>>>>>> get the
>>>>>> following error instead:
>>>>>>
>>>>>>
>>>>>> Running with storage root
>>>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>>>> Running with locale: en_US.UTF-8
>>>>>> Running in the untrusted security domain
>>>>>> Error verifying method org/berk/GroceryList startApp()V
>>>>>> [...]
>>>>>> ALERT: java/lang/VerifyError: org/berk/GroceryList.
>>>>>> Execution completed.
>>>>>> 2750987 bytecodes executed
>>>>>> 32 thread switches
>>>>>> 1666 classes in the system (including system classes)
>>>>>> 14313 dynamic objects allocated (438588 bytes)
>>>>>> 2 garbage collections (378116 bytes collected).
>>>>>>
>>
>>
>>
>>
>>
>>>>>> I really do not know what else I can try, or what other  
>>>>>> diagnostic
>>>>>> information I can send you that could be of help. I heard the  
>>>>>> log mode
>>>>>> of EclipseME could be useful, but I couldn't find a way of  
>>>>>> enabling it.
>>>>>>
>>>>>> If you have any leads, please let me know,
>>>>>>
>>>>>> Sincerely,
>>>>>> Berk
>>>>>>
>>>>>>
>>>>>>
>>>>> -------------------------------------------------------------------------
>>>>>
>>>>>> Check out the new SourceForge.net Marketplace.
>>>>>> It's the best place to buy or sell services for
>>>>>> just about anything Open Source.
>>>>>> http://sourceforge.net/services/buy/index.php
>>>>>> _______________________________________________
>>>>>> Eclipseme-users mailing list
>>>>>> Ecl...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>>>>
>>>>>>
>>>>> -------------------------------------------------------------------------
>>>>> Check out the new SourceForge.net Marketplace.
>>>>> It's the best place to buy or sell services for
>>>>> just about anything Open Source.
>>>>> http://sourceforge.net/services/buy/index.php
>>>>> _______________________________________________
>>>>> Eclipseme-users mailing list
>>>>> Ecl...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>>>
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>> _______________________________________________
>>> Eclipseme-users mailing list
>>> Ecl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>
>>>
>>>
>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>
>>
>>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[Markus S. <si...@ps...>]

> 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 
> regenerated the next round, but I suppose that wasn't the case, since I 
> kept seeing FileNotFound exceptions in the EclipseME console.
That kind of problems always occur in eclipse if you delete folders NOT
using eclipse. If you go to resource view, update it (F5) and then try
again, it should work, because then eclipse "knows" about the current
filesystem. If not, I suggest opening a bugreport.

Thats very annoying about eclipse.

> I apologize for making a novice mistake like this, but I am indeed a 
> beginner and have been developing for this platform for about 3 days. On 
> the flip side, I learned a lot about writing programs for this platform, 
> and I hopefully won't be wasting your time with inconsequential problems 
> (I'll be wasting it with more difficult ones).
I think all of us had similar problems :-)


-- 

*********************************
si...@ps...
http://www.psitronic.de

psitronic IT-Solutions
Markus Sinner
W-Rathenau-Str. 14 - 68642 Bürstadt
Tel.: (+49)6206 / 963513
Fax:  (+49)6206 / 963514

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[Berk B. <ber...@su...>]

PAR...@OR... wrote:
> Berk, final methods are allowed in MIDP. In fact, it's one of the tricks you can use to save a few bytes in the final obfuscated JAR file. I can't say I understand why removing the final method fixed the problems you were seeing, but try adding another final method and see if it works now.
>   
You are absolutely right, it turns out it is the "finalize" method that 
is not allowed. I had it declared the method as "final finalized," and I 
guess I didn't read the error message properly. Initially I was hoping 
to put some code in there that would right my data structure to the RMS 
when my model class was destroyed. It got fixed when I removed the class 
altogether. Thanks for pointing that out!


> Parag Chandra
> Senior Software Developer
> par...@or...
> 404-439-5821
> -----Original Message-----
> From: Berk Birand [mailto:ber...@su...] 
> Sent: Tuesday, June 24, 2008 6:46 AM
> To: ecl...@li...
> 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 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 
> regenerated the next round, but I suppose that wasn't the case, since I 
> kept seeing FileNotFound exceptions in the EclipseME console.
>
> After that was done, the content of the folders were created as 
> expected, but I still got the ClassNotFound exception. Looking at the 
> preverifier output, I realized that was because I had a method declared 
> as "final," which apparently is not allowed in MIDP. Once I took that 
> out, the classes were preverified, and the emulator ran normally.
>
> I apologize for making a novice mistake like this, but I am indeed a 
> beginner and have been developing for this platform for about 3 days. On 
> the flip side, I learned a lot about writing programs for this platform, 
> and I hopefully won't be wasting your time with inconsequential problems 
> (I'll be wasting it with more difficult ones).
>
> Thanks to everyone who have answered,
> Sincerely,
>   Berk
>
> Berk Birand wrote:
>   
>> First of all, thanks a lot for all your quick answers. This has been 
>> really bugging me, and it is somewhat nice to hear that the solution 
>> doesn't stem from me having something configured improperly.
>>
>> After learning about the .eclipseme.tmp directory, I made some more 
>> observations that might be of help. I removed the content of the /bin 
>> directory, and the .eclipseme.tmp directories, as explained in 
>> http://eclipseme.org/docs/buildingRef.html . I then opened Eclipse, and 
>> attempted to re-build the project, getting the same ClassPathNotFound 
>> exception. However when I then check in those directories, I don't see 
>> any new .class files, so nothing appears to have been compiled. There is 
>> a .jar file in the /emulation subfolder, but it only contains a 
>> MANIFEST.MF file.
>>
>> In short, the reason why it cannot find the class is because the sources 
>> are never compiled, not because they are unreachable.
>>
>> Does anybody know why EclipseME would refuse to compile the project? How 
>>   can I force it to do that? Or is there any way to diagnose why it is 
>> not doing so?
>>
>>
>> I enabled the EclipseME debug mode by using the command-line switch, but 
>> the EclipseME error console only displays this:
>>
>>  > PreverificationBuilder.getRuntimeJar project = P/GroceryList
>> < PreverificationBuilder.getRuntimeJar project = P/GroceryList
>>
>> Thank you in advance,
>>   Berk
>>
>>
>> Heiko Selber wrote:
>>     
>>> BTW: Putting /bin into the classpath shouldn't help anyway, because MIDlets must be preverified. So, if anyting, you should add /verified, not /bin.
>>>
>>> As to the original problem: For some reason, over the air doesn't always work for me (perhaps because of missing write permissions).
>>>
>>> But when I do J2ME -> Create Package and specify the MIDlet explicitly in the launch configuration, I can run it in the emulator. 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 <si...@ps...>
>>>> An: ecl...@li...
>>>> 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 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. 
>>>>> 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 of changes to the source code of my own application, and 
>>>>> wanted to see how it worked in the emulator. When I ran the project, 
>>>>> none of the changes showed up, and I would still see some sysout prints 
>>>>> that I had removed long ago. I then went into the Eclipse workspace, and
>>>>> removed the content of the /bin directory, thinking that it would 
>>>>> recompile everything from the source.
>>>>>
>>>>> Instead, I started running into these errors:
>>>>>
>>>>> Running with storage root 
>>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>>> Running with locale: en_US.UTF-8
>>>>> Running in the untrusted security domain
>>>>> java.lang.ClassNotFoundException: org/berk/GroceryList
>>>>>     at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>>>>>     at com.sun.midp.midlet.Scheduler.schedule(+52)
>>>>>     at com.sun.midp.main.Main.runLocalClass(+28)
>>>>>     at com.sun.midp.main.Main.main(+80)
>>>>> Execution completed.
>>>>> 2755738 bytecodes executed
>>>>> 40 thread switches
>>>>> 1665 classes in the system (including system classes)
>>>>> 14243 dynamic objects allocated (437872 bytes)
>>>>> 1 garbage collections (0 bytes collected)
>>>>>
>>>>> Somebody else had a similar problem, and they proposed including the 
>>>>> /bin directory as an "Extra Emulator Parameter" using the -cp switch. 
>>>>> When I do, the emulator does manage to find the class, but I get the 
>>>>> following error instead:
>>>>>
>>>>>
>>>>> Running with storage root 
>>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>>> Running with locale: en_US.UTF-8
>>>>> Running in the untrusted security domain
>>>>> Error verifying method org/berk/GroceryList startApp()V
>>>>> [...]
>>>>> ALERT: java/lang/VerifyError: org/berk/GroceryList.
>>>>> Execution completed.
>>>>> 2750987 bytecodes executed
>>>>> 32 thread switches
>>>>> 1666 classes in the system (including system classes)
>>>>> 14313 dynamic objects allocated (438588 bytes)
>>>>> 2 garbage collections (378116 bytes collected).
>>>>>           
>
>   
>
>
>   
>>>>> I really do not know what else I can try, or what other diagnostic 
>>>>> information I can send you that could be of help. I heard the log mode 
>>>>> of EclipseME could be useful, but I couldn't find a way of enabling it.
>>>>>
>>>>> If you have any leads, please let me know,
>>>>>
>>>>> Sincerely,
>>>>>  Berk
>>>>>
>>>>>
>>>>>           
>>>> -------------------------------------------------------------------------
>>>>         
>>>>> Check out the new SourceForge.net Marketplace.
>>>>> It's the best place to buy or sell services for
>>>>> just about anything Open Source.
>>>>> http://sourceforge.net/services/buy/index.php
>>>>> _______________________________________________
>>>>> Eclipseme-users mailing list
>>>>> Ecl...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>>>   
>>>>>           
>>>> -------------------------------------------------------------------------
>>>> Check out the new SourceForge.net Marketplace.
>>>> It's the best place to buy or sell services for
>>>> just about anything Open Source.
>>>> http://sourceforge.net/services/buy/index.php
>>>> _______________________________________________
>>>> Eclipseme-users mailing list
>>>> Ecl...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>>         
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>
>>
>>     
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>
>
>   

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[<PAR...@OR...>]

Berk, final methods are allowed in MIDP. In fact, it's one of the tricks you can use to save a few bytes in the final obfuscated JAR file. I can't say I understand why removing the final method fixed the problems you were seeing, but try adding another final method and see if it works now.

Parag Chandra
Senior Software Developer
par...@or...
404-439-5821
-----Original Message-----
From: Berk Birand [mailto:ber...@su...] 
Sent: Tuesday, June 24, 2008 6:46 AM
To: ecl...@li...
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 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 
regenerated the next round, but I suppose that wasn't the case, since I 
kept seeing FileNotFound exceptions in the EclipseME console.

After that was done, the content of the folders were created as 
expected, but I still got the ClassNotFound exception. Looking at the 
preverifier output, I realized that was because I had a method declared 
as "final," which apparently is not allowed in MIDP. Once I took that 
out, the classes were preverified, and the emulator ran normally.

I apologize for making a novice mistake like this, but I am indeed a 
beginner and have been developing for this platform for about 3 days. On 
the flip side, I learned a lot about writing programs for this platform, 
and I hopefully won't be wasting your time with inconsequential problems 
(I'll be wasting it with more difficult ones).

Thanks to everyone who have answered,
Sincerely,
  Berk

Berk Birand wrote:
> First of all, thanks a lot for all your quick answers. This has been 
> really bugging me, and it is somewhat nice to hear that the solution 
> doesn't stem from me having something configured improperly.
> 
> After learning about the .eclipseme.tmp directory, I made some more 
> observations that might be of help. I removed the content of the /bin 
> directory, and the .eclipseme.tmp directories, as explained in 
> http://eclipseme.org/docs/buildingRef.html . I then opened Eclipse, and 
> attempted to re-build the project, getting the same ClassPathNotFound 
> exception. However when I then check in those directories, I don't see 
> any new .class files, so nothing appears to have been compiled. There is 
> a .jar file in the /emulation subfolder, but it only contains a 
> MANIFEST.MF file.
> 
> In short, the reason why it cannot find the class is because the sources 
> are never compiled, not because they are unreachable.
> 
> Does anybody know why EclipseME would refuse to compile the project? How 
>   can I force it to do that? Or is there any way to diagnose why it is 
> not doing so?
> 
> 
> I enabled the EclipseME debug mode by using the command-line switch, but 
> the EclipseME error console only displays this:
> 
>  > PreverificationBuilder.getRuntimeJar project = P/GroceryList
> < PreverificationBuilder.getRuntimeJar project = P/GroceryList
> 
> Thank you in advance,
>   Berk
> 
> 
> Heiko Selber wrote:
>> BTW: Putting /bin into the classpath shouldn't help anyway, because MIDlets must be preverified. So, if anyting, you should add /verified, not /bin.
>>
>> As to the original problem: For some reason, over the air doesn't always work for me (perhaps because of missing write permissions).
>>
>> But when I do J2ME -> Create Package and specify the MIDlet explicitly in the launch configuration, I can run it in the emulator. 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 <si...@ps...>
>>> An: ecl...@li...
>>> 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 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. 
>>>> 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 of changes to the source code of my own application, and 
>>>> wanted to see how it worked in the emulator. When I ran the project, 
>>>> none of the changes showed up, and I would still see some sysout prints 
>>>> that I had removed long ago. I then went into the Eclipse workspace, and
>>>> removed the content of the /bin directory, thinking that it would 
>>>> recompile everything from the source.
>>>>
>>>> Instead, I started running into these errors:
>>>>
>>>> Running with storage root 
>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>> Running with locale: en_US.UTF-8
>>>> Running in the untrusted security domain
>>>> java.lang.ClassNotFoundException: org/berk/GroceryList
>>>>     at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>>>>     at com.sun.midp.midlet.Scheduler.schedule(+52)
>>>>     at com.sun.midp.main.Main.runLocalClass(+28)
>>>>     at com.sun.midp.main.Main.main(+80)
>>>> Execution completed.
>>>> 2755738 bytecodes executed
>>>> 40 thread switches
>>>> 1665 classes in the system (including system classes)
>>>> 14243 dynamic objects allocated (437872 bytes)
>>>> 1 garbage collections (0 bytes collected)
>>>>
>>>> Somebody else had a similar problem, and they proposed including the 
>>>> /bin directory as an "Extra Emulator Parameter" using the -cp switch. 
>>>> When I do, the emulator does manage to find the class, but I get the 
>>>> following error instead:
>>>>
>>>>
>>>> Running with storage root 
>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>> Running with locale: en_US.UTF-8
>>>> Running in the untrusted security domain
>>>> Error verifying method org/berk/GroceryList startApp()V
>>>> [...]
>>>> ALERT: java/lang/VerifyError: org/berk/GroceryList.
>>>> Execution completed.
>>>> 2750987 bytecodes executed
>>>> 32 thread switches
>>>> 1666 classes in the system (including system classes)
>>>> 14313 dynamic objects allocated (438588 bytes)
>>>> 2 garbage collections (378116 bytes collected).

>>>>


>>>>
>>>> I really do not know what else I can try, or what other diagnostic 
>>>> information I can send you that could be of help. I heard the log mode 
>>>> of EclipseME could be useful, but I couldn't find a way of enabling it.
>>>>
>>>> If you have any leads, please let me know,
>>>>
>>>> Sincerely,
>>>>  Berk
>>>>
>>>>
>>> -------------------------------------------------------------------------
>>>> Check out the new SourceForge.net Marketplace.
>>>> It's the best place to buy or sell services for
>>>> just about anything Open Source.
>>>> http://sourceforge.net/services/buy/index.php
>>>> _______________________________________________
>>>> Eclipseme-users mailing list
>>>> Ecl...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>>   
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>> _______________________________________________
>>> Eclipseme-users mailing list
>>> Ecl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 
> 


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Eclipseme-users mailing list
Ecl...@li...
https://lists.sourceforge.net/lists/listinfo/eclipseme-users

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9 [SOLVED]

[Berk B. <ber...@su...>]

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 
regenerated the next round, but I suppose that wasn't the case, since I 
kept seeing FileNotFound exceptions in the EclipseME console.

After that was done, the content of the folders were created as 
expected, but I still got the ClassNotFound exception. Looking at the 
preverifier output, I realized that was because I had a method declared 
as "final," which apparently is not allowed in MIDP. Once I took that 
out, the classes were preverified, and the emulator ran normally.

I apologize for making a novice mistake like this, but I am indeed a 
beginner and have been developing for this platform for about 3 days. On 
the flip side, I learned a lot about writing programs for this platform, 
and I hopefully won't be wasting your time with inconsequential problems 
(I'll be wasting it with more difficult ones).

Thanks to everyone who have answered,
Sincerely,
  Berk

Berk Birand wrote:
> First of all, thanks a lot for all your quick answers. This has been 
> really bugging me, and it is somewhat nice to hear that the solution 
> doesn't stem from me having something configured improperly.
> 
> After learning about the .eclipseme.tmp directory, I made some more 
> observations that might be of help. I removed the content of the /bin 
> directory, and the .eclipseme.tmp directories, as explained in 
> http://eclipseme.org/docs/buildingRef.html . I then opened Eclipse, and 
> attempted to re-build the project, getting the same ClassPathNotFound 
> exception. However when I then check in those directories, I don't see 
> any new .class files, so nothing appears to have been compiled. There is 
> a .jar file in the /emulation subfolder, but it only contains a 
> MANIFEST.MF file.
> 
> In short, the reason why it cannot find the class is because the sources 
> are never compiled, not because they are unreachable.
> 
> Does anybody know why EclipseME would refuse to compile the project? How 
>   can I force it to do that? Or is there any way to diagnose why it is 
> not doing so?
> 
> 
> I enabled the EclipseME debug mode by using the command-line switch, but 
> the EclipseME error console only displays this:
> 
>  > PreverificationBuilder.getRuntimeJar project = P/GroceryList
> < PreverificationBuilder.getRuntimeJar project = P/GroceryList
> 
> Thank you in advance,
>   Berk
> 
> 
> Heiko Selber wrote:
>> BTW: Putting /bin into the classpath shouldn't help anyway, because MIDlets must be preverified. So, if anyting, you should add /verified, not /bin.
>>
>> As to the original problem: For some reason, over the air doesn't always work for me (perhaps because of missing write permissions).
>>
>> But when I do J2ME -> Create Package and specify the MIDlet explicitly in the launch configuration, I can run it in the emulator. 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 <si...@ps...>
>>> An: ecl...@li...
>>> 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 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. 
>>>> 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 of changes to the source code of my own application, and 
>>>> wanted to see how it worked in the emulator. When I ran the project, 
>>>> none of the changes showed up, and I would still see some sysout prints 
>>>> that I had removed long ago. I then went into the Eclipse workspace, and
>>>> removed the content of the /bin directory, thinking that it would 
>>>> recompile everything from the source.
>>>>
>>>> Instead, I started running into these errors:
>>>>
>>>> Running with storage root 
>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>> Running with locale: en_US.UTF-8
>>>> Running in the untrusted security domain
>>>> java.lang.ClassNotFoundException: org/berk/GroceryList
>>>>     at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>>>>     at com.sun.midp.midlet.Scheduler.schedule(+52)
>>>>     at com.sun.midp.main.Main.runLocalClass(+28)
>>>>     at com.sun.midp.main.Main.main(+80)
>>>> Execution completed.
>>>> 2755738 bytecodes executed
>>>> 40 thread switches
>>>> 1665 classes in the system (including system classes)
>>>> 14243 dynamic objects allocated (437872 bytes)
>>>> 1 garbage collections (0 bytes collected)
>>>>
>>>> Somebody else had a similar problem, and they proposed including the 
>>>> /bin directory as an "Extra Emulator Parameter" using the -cp switch. 
>>>> When I do, the emulator does manage to find the class, but I get the 
>>>> following error instead:
>>>>
>>>>
>>>> Running with storage root 
>>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>>> Running with locale: en_US.UTF-8
>>>> Running in the untrusted security domain
>>>> Error verifying method org/berk/GroceryList startApp()V
>>>> [...]
>>>> ALERT: java/lang/VerifyError: org/berk/GroceryList.
>>>> Execution completed.
>>>> 2750987 bytecodes executed
>>>> 32 thread switches
>>>> 1666 classes in the system (including system classes)
>>>> 14313 dynamic objects allocated (438588 bytes)
>>>> 2 garbage collections (378116 bytes collected).

>>>>


>>>>
>>>> I really do not know what else I can try, or what other diagnostic 
>>>> information I can send you that could be of help. I heard the log mode 
>>>> of EclipseME could be useful, but I couldn't find a way of enabling it.
>>>>
>>>> If you have any leads, please let me know,
>>>>
>>>> Sincerely,
>>>>  Berk
>>>>
>>>>
>>> -------------------------------------------------------------------------
>>>> Check out the new SourceForge.net Marketplace.
>>>> It's the best place to buy or sell services for
>>>> just about anything Open Source.
>>>> http://sourceforge.net/services/buy/index.php
>>>> _______________________________________________
>>>> Eclipseme-users mailing list
>>>> Ecl...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>>   
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>> _______________________________________________
>>> Eclipseme-users mailing list
>>> Ecl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 
> 

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9

[Berk B. <ber...@su...>]

First of all, thanks a lot for all your quick answers. This has been 
really bugging me, and it is somewhat nice to hear that the solution 
doesn't stem from me having something configured improperly.

After learning about the .eclipseme.tmp directory, I made some more 
observations that might be of help. I removed the content of the /bin 
directory, and the .eclipseme.tmp directories, as explained in 
http://eclipseme.org/docs/buildingRef.html . I then opened Eclipse, and 
attempted to re-build the project, getting the same ClassPathNotFound 
exception. However when I then check in those directories, I don't see 
any new .class files, so nothing appears to have been compiled. There is 
a .jar file in the /emulation subfolder, but it only contains a 
MANIFEST.MF file.

In short, the reason why it cannot find the class is because the sources 
are never compiled, not because they are unreachable.

Does anybody know why EclipseME would refuse to compile the project? How 
  can I force it to do that? Or is there any way to diagnose why it is 
not doing so?


I enabled the EclipseME debug mode by using the command-line switch, but 
the EclipseME error console only displays this:

 > PreverificationBuilder.getRuntimeJar project = P/GroceryList
< PreverificationBuilder.getRuntimeJar project = P/GroceryList

Thank you in advance,
  Berk


Heiko Selber wrote:
> BTW: Putting /bin into the classpath shouldn't help anyway, because MIDlets must be preverified. So, if anyting, you should add /verified, not /bin.
> 
> As to the original problem: For some reason, over the air doesn't always work for me (perhaps because of missing write permissions).
> 
> But when I do J2ME -> Create Package and specify the MIDlet explicitly in the launch configuration, I can run it in the emulator. 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 <si...@ps...>
>> An: ecl...@li...
>> 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 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. 
>>> 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 of changes to the source code of my own application, and 
>>> wanted to see how it worked in the emulator. When I ran the project, 
>>> none of the changes showed up, and I would still see some sysout prints 
>>> that I had removed long ago. I then went into the Eclipse workspace, and
>>> removed the content of the /bin directory, thinking that it would 
>>> recompile everything from the source.
>>>
>>> Instead, I started running into these errors:
>>>
>>> Running with storage root 
>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>> Running with locale: en_US.UTF-8
>>> Running in the untrusted security domain
>>> java.lang.ClassNotFoundException: org/berk/GroceryList
>>>     at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>>>     at com.sun.midp.midlet.Scheduler.schedule(+52)
>>>     at com.sun.midp.main.Main.runLocalClass(+28)
>>>     at com.sun.midp.main.Main.main(+80)
>>> Execution completed.
>>> 2755738 bytecodes executed
>>> 40 thread switches
>>> 1665 classes in the system (including system classes)
>>> 14243 dynamic objects allocated (437872 bytes)
>>> 1 garbage collections (0 bytes collected)
>>>
>>> Somebody else had a similar problem, and they proposed including the 
>>> /bin directory as an "Extra Emulator Parameter" using the -cp switch. 
>>> When I do, the emulator does manage to find the class, but I get the 
>>> following error instead:
>>>
>>>
>>> Running with storage root 
>>> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
>>> Running with locale: en_US.UTF-8
>>> Running in the untrusted security domain
>>> Error verifying method org/berk/GroceryList startApp()V
>>> [...]
>>> ALERT: java/lang/VerifyError: org/berk/GroceryList.
>>> Execution completed.
>>> 2750987 bytecodes executed
>>> 32 thread switches
>>> 1666 classes in the system (including system classes)
>>> 14313 dynamic objects allocated (438588 bytes)
>>> 2 garbage collections (378116 bytes collected).
>>>
>>>
>>> I really do not know what else I can try, or what other diagnostic 
>>> information I can send you that could be of help. I heard the log mode 
>>> of EclipseME could be useful, but I couldn't find a way of enabling it.
>>>
>>> If you have any leads, please let me know,
>>>
>>> Sincerely,
>>>  Berk
>>>
>>>
>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://sourceforge.net/services/buy/index.php
>>> _______________________________________________
>>> Eclipseme-users mailing list
>>> Ecl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>>   
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> 

Re: [Eclipseme-users] A question about the preprocessing hook

[Setera C. <cra...@se...>]

It has been a long time ago, but if I remember correctly it was  
necessary due to the way that the OSGi layer loads jar files during  
this early phase.

On Jun 20, 2008, at 11:08 AM, Raymond Qiu wrote:

> Craig,
>
> Why did you put the ASM source code into the hook plug-in but not
> just use its jar lib? I tried to replace the source files with the
> asm.jar. The hook plug-in could be compiled but got some exception
> when eclipse started. The log said
> " java.lang.NoClassDefFoundError: org/objectweb/asm/ClassVisitor".
>
> Thanks. :-)
>
> - Raymond
>
> -----Original Message-----
> From: ecl...@li...
> [mailto:ecl...@li...] On Behalf Of
> Setera Craig
> Sent: Thursday, June 19, 2008 2:17 PM
> To: ecl...@li...
> Subject: Re: [Eclipseme-users] A question about the preprocessing hook
>
> I didn't write the actual preprocessor... I had one originally that I
> removed in favor of the one written for the Antenna tools.  Obviously,
> Antenna doesn't want to have a dependency on the Eclipse DOM/AST,
> although I know it is somewhat separable.
>
> On Jun 19, 2008, at 1:12 PM, Raymond Qiu wrote:
>
>> In other words, why don't you use eclipse DOM/AST?
>>
>> - Raymond
>>
>> -----Original Message-----
>> From: ecl...@li...
>> [mailto:ecl...@li...] On Behalf Of
>> Raymond Qiu
>> Sent: Thursday, June 19, 2008 12:10 PM
>> To: ecl...@li...
>> Subject: [Eclipseme-users] A question about the preprocessing hook
>>
>> Craig,
>>
>> I am pretty interested in the preprocessing function in eclipseme.
>> I read its code and I am wondering why you used ASM when rewriting
>> the byte of a java file?
>>
>> Thanks.
>>
>> - Raymond
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain  
>> confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute
>> non-public information. Any use of this information by anyone other
>> than
>> the intended recipient is prohibited. If you have received this
>> transmission in error, please immediately reply to the sender and
>> delete
>> this information from your system. Use, dissemination, distribution,
>> or
>> reproduction of this transmission by unintended recipients is not
>> authorized and may be unlawful.
>>
>>
> ------------------------------------------------------------------------
>> -
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain
>> confidential information, privileged material (including material
>> protected by the solicitor-client or other applicable privileges),
>> or constitute non-public information. Any use of this information by
>> anyone other than the intended recipient is prohibited. If you have
>> received this transmission in error, please immediately reply to the
>> sender and delete this information from your system. Use,
>> dissemination, distribution, or reproduction of this transmission by
>> unintended recipients is not authorized and may be unlawful.
>>
>>
> ------------------------------------------------------------------------
> -
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://sourceforge.net/services/buy/index.php
>> _______________________________________________
>> Eclipseme-users mailing list
>> Ecl...@li...
>> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>
>
> ------------------------------------------------------------------------
> -
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>
> ---------------------------------------------------------------------
> This transmission (including any attachments) may contain  
> confidential information, privileged material (including material  
> protected by the solicitor-client or other applicable privileges),  
> or constitute non-public information. Any use of this information by  
> anyone other than the intended recipient is prohibited. If you have  
> received this transmission in error, please immediately reply to the  
> sender and delete this information from your system. Use,  
> dissemination, distribution, or reproduction of this transmission by  
> unintended recipients is not authorized and may be unlawful.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9

[Setera C. <cra...@se...>]

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 
  .

Craig

On Jun 23, 2008, at 3:58 PM, Berk Birand wrote:

> 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 of changes to the source code of my own application, and
> wanted to see how it worked in the emulator. When I ran the project,
> none of the changes showed up, and I would still see some sysout  
> prints
> that I had removed long ago. I then went into the Eclipse workspace,  
> and
> removed the content of the /bin directory, thinking that it would
> recompile everything from the source.
>
> Instead, I started running into these errors:
>
> Running with storage root
> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
> Running with locale: en_US.UTF-8
> Running in the untrusted security domain
> java.lang.ClassNotFoundException: org/berk/GroceryList
>    at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>    at com.sun.midp.midlet.Scheduler.schedule(+52)
>    at com.sun.midp.main.Main.runLocalClass(+28)
>    at com.sun.midp.main.Main.main(+80)
> Execution completed.
> 2755738 bytecodes executed
> 40 thread switches
> 1665 classes in the system (including system classes)
> 14243 dynamic objects allocated (437872 bytes)
> 1 garbage collections (0 bytes collected)
>
> Somebody else had a similar problem, and they proposed including the
> /bin directory as an "Extra Emulator Parameter" using the -cp switch.
> When I do, the emulator does manage to find the class, but I get the
> following error instead:
>
>
> Running with storage root
> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
> Running with locale: en_US.UTF-8
> Running in the untrusted security domain
> Error verifying method org/berk/GroceryList startApp()V
> [...]
> ALERT: java/lang/VerifyError: org/berk/GroceryList.
> Execution completed.
> 2750987 bytecodes executed
> 32 thread switches
> 1666 classes in the system (including system classes)
> 14313 dynamic objects allocated (438588 bytes)
> 2 garbage collections (378116 bytes collected).
>
>
> I really do not know what else I can try, or what other diagnostic
> information I can send you that could be of help. I heard the log mode
> of EclipseME could be useful, but I couldn't find a way of enabling  
> it.
>
> If you have any leads, please let me know,
>
> Sincerely,
> Berk
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9

[Heiko S. <hei...@gm...>]

BTW: Putting /bin into the classpath shouldn't help anyway, because MIDlets must be preverified. So, if anyting, you should add /verified, not /bin.

As to the original problem: For some reason, over the air doesn't always work for me (perhaps because of missing write permissions).

But when I do J2ME -> Create Package and specify the MIDlet explicitly in the launch configuration, I can run it in the emulator. 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 <si...@ps...>
> An: ecl...@li...
> 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 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. 
> > 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 of changes to the source code of my own application, and 
> > wanted to see how it worked in the emulator. When I ran the project, 
> > none of the changes showed up, and I would still see some sysout prints 
> > that I had removed long ago. I then went into the Eclipse workspace, and
> > removed the content of the /bin directory, thinking that it would 
> > recompile everything from the source.
> >
> > Instead, I started running into these errors:
> >
> > Running with storage root 
> > /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
> > Running with locale: en_US.UTF-8
> > Running in the untrusted security domain
> > java.lang.ClassNotFoundException: org/berk/GroceryList
> >     at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
> >     at com.sun.midp.midlet.Scheduler.schedule(+52)
> >     at com.sun.midp.main.Main.runLocalClass(+28)
> >     at com.sun.midp.main.Main.main(+80)
> > Execution completed.
> > 2755738 bytecodes executed
> > 40 thread switches
> > 1665 classes in the system (including system classes)
> > 14243 dynamic objects allocated (437872 bytes)
> > 1 garbage collections (0 bytes collected)
> >
> > Somebody else had a similar problem, and they proposed including the 
> > /bin directory as an "Extra Emulator Parameter" using the -cp switch. 
> > When I do, the emulator does manage to find the class, but I get the 
> > following error instead:
> >
> >
> > Running with storage root 
> > /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
> > Running with locale: en_US.UTF-8
> > Running in the untrusted security domain
> > Error verifying method org/berk/GroceryList startApp()V
> > [...]
> > ALERT: java/lang/VerifyError: org/berk/GroceryList.
> > Execution completed.
> > 2750987 bytecodes executed
> > 32 thread switches
> > 1666 classes in the system (including system classes)
> > 14313 dynamic objects allocated (438588 bytes)
> > 2 garbage collections (378116 bytes collected).
> >
> >
> > I really do not know what else I can try, or what other diagnostic 
> > information I can send you that could be of help. I heard the log mode 
> > of EclipseME could be useful, but I couldn't find a way of enabling it.
> >
> > If you have any leads, please let me know,
> >
> > Sincerely,
> >  Berk
> >
> >
> -------------------------------------------------------------------------
> > Check out the new SourceForge.net Marketplace.
> > It's the best place to buy or sell services for
> > just about anything Open Source.
> > http://sourceforge.net/services/buy/index.php
> > _______________________________________________
> > Eclipseme-users mailing list
> > Ecl...@li...
> > https://lists.sourceforge.net/lists/listinfo/eclipseme-users
> >   
> 
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users

-- 
----
I condem'n the abuse of apostrophe's.


Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten 
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser

Re: [Eclipseme-users] ClassNotFound problem with Eclipse 3.3 and EclipseME 1.7.9

[Markus S. <si...@ps...>]

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. 
> 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 of changes to the source code of my own application, and 
> wanted to see how it worked in the emulator. When I ran the project, 
> none of the changes showed up, and I would still see some sysout prints 
> that I had removed long ago. I then went into the Eclipse workspace, and 
> removed the content of the /bin directory, thinking that it would 
> recompile everything from the source.
>
> Instead, I started running into these errors:
>
> Running with storage root 
> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
> Running with locale: en_US.UTF-8
> Running in the untrusted security domain
> java.lang.ClassNotFoundException: org/berk/GroceryList
>     at com.sun.midp.midlet.MIDletState.createMIDlet(+29)
>     at com.sun.midp.midlet.Scheduler.schedule(+52)
>     at com.sun.midp.main.Main.runLocalClass(+28)
>     at com.sun.midp.main.Main.main(+80)
> Execution completed.
> 2755738 bytecodes executed
> 40 thread switches
> 1665 classes in the system (including system classes)
> 14243 dynamic objects allocated (437872 bytes)
> 1 garbage collections (0 bytes collected)
>
> Somebody else had a similar problem, and they proposed including the 
> /bin directory as an "Extra Emulator Parameter" using the -cp switch. 
> When I do, the emulator does manage to find the class, but I get the 
> following error instead:
>
>
> Running with storage root 
> /home/graffiti/j2mewtk/2.5.2/appdb/DefaultColorPhone
> Running with locale: en_US.UTF-8
> Running in the untrusted security domain
> Error verifying method org/berk/GroceryList startApp()V
> [...]
> ALERT: java/lang/VerifyError: org/berk/GroceryList.
> Execution completed.
> 2750987 bytecodes executed
> 32 thread switches
> 1666 classes in the system (including system classes)
> 14313 dynamic objects allocated (438588 bytes)
> 2 garbage collections (378116 bytes collected).
>
>
> I really do not know what else I can try, or what other diagnostic 
> information I can send you that could be of help. I heard the log mode 
> of EclipseME could be useful, but I couldn't find a way of enabling it.
>
> If you have any leads, please let me know,
>
> Sincerely,
>  Berk
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> Eclipseme-users mailing list
> Ecl...@li...
> https://lists.sourceforge.net/lists/listinfo/eclipseme-users
>