This is way more of a feature request than anything else, but I wanted
to get thoughts on this before I try and hack eclipseme and make a
patch.
Here's the problem:
Using microemulator, I can get complete junit testing of my MIDP apps.
Yay!
This causes a bunch of problems with preverification (naturally) since
micro / junit uses J2SE and reflection and all the other goodies not
available in ME.
At the same time, I want to retain the ability to do real emulator
(paradox?) testing via eclipseME.
Here's my current solution:
Add microemulator as a dependency (I'm using maven, so it's a
scope=provided dependency).
Turn preverification off for unit testing and running the app within
micro emu.
Turn preverification on but take src/test/java off the build path in
order to build for the real emulator.
Run the midlet using eclipse me / obfuscate / all the other fun things.
This is a bit painful.
Here is my proposed solution:
Add an option to EclipseME to ignore preverifying certain paths. In my
case, this would "src/test/java, microemulator.jar". This is perfectly
fine since running the app under eclipseME using the regular emulator
never touches any of the classes in src/test anyway or any of the
microemulator classes and so I won't see the dreaded "class not found"
errors.
Thoughts? Am I nuts? Is there an easier way of doing this?
Thanks a lot!
-Rushabh
--
Rushabh Doshi
http://keeda.stanford.edu/~radoshi
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Eclipseme-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
