Hello, When using JDEE for J2ME development, it is not very convenient that the classpath always includes the Java SE JRE rt.jar (even if it's not present in jde-global-classpath), since it renders the class name qualification algorithm more ambiguous.
For instance, if I try to complete the class 'Image', I need to specify if I denote java.awt.Image or javax.microedition.lcdui.Image, even though the former class isn't present in J2ME. This also confuses the automatic adder of import statements. Would would be the best solution to solve this? One solution would be to set up some kind of separate profiles (defining the above classpath) for Java SE and J2ME development along the lines of jde-jdk-registry, but this seems a bit overkill to me. -Tobias ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
