Thanks guys. Understood now that these are unrelated issues.
The problem with the eclipseme.tmp/emulator JAD and JAR not showing up for
work, or not being updated when the project builds doesn't happen
consistently, so it hasn't stopped me dead in my tracks. I'll try to figure
out the pattern and will read the building reference and troubleshooting
pages.
Meantime I have another slightly OT question, that I'll post in a separate
thread.
-David
On 9/12/07, Craig Setera <[EMAIL PROTECTED]> wrote:
>
> David,
>
> Markus is right that the Ant build scripts should have nothing to do
> with the builder functionality. The Ant export is just a way to get a
> working build file to start with. Beyond that, those files should be
> completely separate from the builder. I realize that this is a bit
> different than the way that Netbeans works.
>
> In addition to the link that Markus sent, I'd ask you to also take a
> look at http://eclipseme.org/docs/buildingRef.html and use the tools on
> that page to take a look at what is happening during the build.
>
> Thanks,
> Craig
>
> Markus Sinner wrote:
> > Hello David,
> >
> > you mean, that the changes in the xml-files for ant affected the
> > possibility to run or debug the app from INSIDE eclipse? I cannot
> > understand the conjunction, as the internal build-process has nothing to
> > do with the xml-files used by ant. But if you run the emulator/debug
> > with ant, than you have to be sure that the jad/jar is at the place you
> > specify in your xml-files.
> >
> > Can you append some traces/logs? Look here:
> > http://eclipseme.org/docs/troubleshooting.html
> >
> > I am out of office for some days, so maybe someone else should answer
> > your answers :-)
> >
> > Markus
> >
> > David Beers schrieb:
> >
> >> 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
> >>
> >>
> >
> >
> >
> -------------------------------------------------------------------------
> > 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
> >
>
> -------------------------------------------------------------------------
> 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
>
--
David Beers
Pikesoft Mobile Computing
www.pikesoft.com
-------------------------------------------------------------------------
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
