Hi Craig, I get an enormous amount of value out of EclipseME, and I greatly appreciate your excellent work in developing and maintaining it.
To me, EclipseME is the clearly *the* plugin for serious J2ME development in Eclipse. Considering all the funds pouring into alternative tools from the vendors, its a great credit to yourself that, basically singlehandedly, you have been able to integrate the Eclipse core and numerous 3rd party tools and libraries to synthesize such a powerful toolset. As for 1.7.0, well... stuff happens. Ive created some shocking bugs in my career. All you can do is learn from experience and move on. I hope that you will continue to manage EclipseME, but if you do find yourself wanting to move on, I hope the tool can form the basis of the Eclipse Foundation's official toolset for J2ME (named MTJ or otherwise). Otherwise, we may see a repeat of the java.util.logging fiasco, where the widely used OS tool Log4j was scorned by Sun, only to see their official but inferior alternative ignored by the community. -Ben Craig Setera wrote: >Ben, > >"In hindsight, the problems reported by Markus Sinner on 14/6 perhaps ought to >have stalled release >of 1.7.0 until they were resolved." > >Yes, without a doubt, 1.7.0 turned out to be a bad release. Too bad hindsight >is so much more clear. I'm very proud of the work that I do on EclipseME and >regret that 1.7.0 has turned out to be such a mess. It was unfortunate. I >lost the original email that Markus sent and there was no bug report. I'm not >trying to point fingers, but in the future we need to make sure there are bugs >in the tracker to avoid that potential problem. The amount of time I have for >EclipseME has dwindled as the complexity has continued to increase. > >Is this still a worthwhile tool for everyone, even if there are a few >bad releases along the way? I'm really excited to see all of you >jumping in to test things and I think it could be very helpful to the >quality of the releases. Heaven knows that I need all of the help that >I can get at this point. This is a turning point for this project. It >appears that the Eclipse MTJ project is not going to get off the >ground. That leaves me with a lot of pressure to keep EclipseME going >and yet I'm tired and frustrated with trying to keep EclipseME going. >Releases like this don't help. > >Thoughts appreciated, >Craig > >Ben Hutchison wrote: > > >>Marcel Ruff wrote: >> >> >> >> >>>But obfuscation suddenly doesn't work anymore: >>>Clicking 'Create Package' and 'Create Obfuscated Package' both produce >>>an unobfuscated result. >>> >>> >>> >>> >>> >>I have identified 2 problems with obfuscation in 1.7.0.b in my >>environment (Eclipse 3.3.0 Windows): >> >>1. The generated JAD file shows the JAR size unobfuscated, and does not >>match the true JAR size. >> >>2. Apparently, every 2nd run of the obfuscator does not obfuscate. >> >>It does seem that 1.7.0 is broken at present. In hindsight, the problems >>reported by Markus Sinner on 14/6 perhaps ought to have stalled release >>of 1.7.0 until they were resolved. >> >>-Ben >> >> >> >> > >------------------------------------------------------------------------- >This SF.net email is sponsored by DB2 Express >Download DB2 Express C - the FREE version of DB2 express and take >control of your XML. No limits. Just data. Click to get it now. >http://sourceforge.net/powerbar/db2/ >_______________________________________________ >Eclipseme-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/eclipseme-users > > > > -- Ben Hutchison Lead Developer Playscape Games http://www.playscapegames.com ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Eclipseme-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/eclipseme-users
