I'm working with a wireless dev team that is using a bunch of different IDEs
(Eclipse, NetBeans, IntelliJ) as well as a couple different platforms
(Windows and OSX). Yeah, I know. :-) Anyway, to get an Ant build that will
work fine in any of our environments and to handle special requirements
(like multi-target builds) we had to ditch the build.xml,
eclipseme-build.xml, and eclipseme-build.properties that EclipseME generates
in favor of a custom build.xml.
Once we got this working we found that our EclipseME users had lost the
ability to run or debug the project from an Eclipse runtime configuration.
Further examination showed that the problem was that the JAD and JAR were
not being copied to the .eclipseme.tmp/emulator directory before the the
emulator runs. So my question is this: assuming this is because of our
messing around with the build files, what would I need to do to our custom
build file (aside from reverting completely to the ones that EclipseME
exports) to get it to support the normal pre-launch behavior of our launch
configurations?
Or is there something else that might account for the aforementioned
failure?
Since I suppose we're not really using EclipseME quite as it was intended,
we're open to weird workarounds. Anything to get this working for us!
--
David Beers
MapQuest Wireless
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Eclipseme-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
