Markus Sinner wrote: > What do you mean with "the JAD file still specifies the original > Midlet filename "Arcadia.jar"" ?
I mean the JAR URL.specifies the original Midlet filename "Arcadia.jar". > The JAD only specifies the Classname of the midlet to run, and maybe a > JAR-URL from which to download the JAR. The last parameter, > Midlet-JAR-URL can be changed and saved in the eclipseME-JAD Editor. > > I think that the output-Jar is named according to the JAD. Try > rightclick->Refactor->Rename on the JAD and rename it to > ArcadiaM3.jad, then the JAR should be ArcadiaM3.jar. The behavior I am seeing contradicts your belief. The Jad file is named Arcadia.JAD, while the resultant JAR is named ArcadiaM3.jar. There is no artefact in the project containing the string ArcadiaM3, since I made up that name only when creating the project to load the checked out code into. That is why I think the output JAR is in fact a function of the Eclipse project name. Thats consistent with whats stated in EclipseME help. But EclipseME help suggests that if you change the Jar URL, that will change the output jar filename. Its that last bit that doesnt seem to happen. -Ben -- Ben Hutchison Lead Developer Playscape Games http://www.playscapegames.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
