I noticed something else just now that makes me think both issues I reported today might be related: the output JAD file has only one attribute in it: midlet jar size. All others are missing.
Lets revise position: Project: "ArcadiaM3" checked out from source code branch for previous project "Arcadia" Contains file template "Arcadia.jad" Generates outputs ArcadiaM3.jar and ArcadiaM3.jad ArcadiaM3.jad has only 1 attribute, jar size (which is dynamically generated) ArcadiaM3.jar has no manifest. It can all be exaplained if we assume that build process looked for a template named ArcadiaM3.jad, which wasnt there of course. So, if the build process can be fixed, to look for Jad file corresponding to midlet URL, it may all work. EclipseME surely should allow multiple side-by-side projects, each differently named, derived from same project code, to enable check outs of old versions/branches for maintenance etc. I would also suggest more error checking in code (eg perhaps missing Jad template file, zero mainfest attributes?) would help to detect & report to user such a non-sensical situation. Anyway, right now, this is just a guess as to whats happening. Im not familar with EclipseME code. -Ben Ben Hutchison wrote: >Today, I checked out an old branch of a long running EclipseMe project, >and created a new Eclipse project from it. > >I did it via "New Java Project" -> From existing source., rather than >Import, because I couldnt get import to recognize the checked out code >as a project dir (despite having a .project file in it). Strange... > >Anyway, everything seemed to work ok at first (except see my recent >email). However, when I build an obfuscated Jar from the project, I find >that the output Jar has no manifest and is thus invalid. (Previously >this is always working fine for the same project.) > >It would be good to figure out what has prevented EclipseME from >generating the manifest. > >Also, may I suggest that EclipseME complains a bit louder if it >cannot/did not generate the manifest. Not having one means a totally >broken jar, yet I saw no error on screen or in Eclipse log. > >One possible explanation: the branch is about 1 month old. I think when >it was created, I was running Eclipse 3.2.2, EclipseME 1.6.x, and now >when I check out, I have upgraded to Eclipse 3.3 and EclipseME 1.7.6. >Perhaps such version differences are causing (i) inability to import, or >(ii) failure to generate manifest. > >Do you think it is a likely reason, Craig? > >-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
