This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
[ JDK VERSION : J2SE 1.5.0 ] After using Library Manager to point to the files required for mobility development, the IDE apparently doesn't want to recognize them. I assume defining them in the library is the same as mounting them was in 3.6, you basically put them on the classpath, right? The classes I am in need of ARE in the two jar files. Why can't the compiler resolve it? I assumed libraries, jars, etc defined at this level would be IDE-wide, ie, not project specific. I guess this is not the case, as by placing the two jars you see below at the project level, it works. Is this normal behavior or am I doing something wrong? I would certainly prefer not to have to define these (and others) for each and every project. Please advise... ===Library Manager=== jar:file:/C:/WTK22/lib/cldcapi10.jar!/ jar:file:/C:/WTK22/lib/midpapi10.jar!/ file:/C:/WTK22/lib/lib ===Compiler Output=== init: deps-jar: Compiling 1 source file to C:\Documents and Settings\Owner\NetbeansDev\build\classes C:\NetBeansDev\dir\mapMagic.java:12: package javax.microedition.io does not exist import javax.microedition.io.*; C:\NetBeansDev\dir\mapMagic.java:13: package javax.microedition.lcdui does not exist import javax.microedition.lcdui.*;
well, if the goal is development of J2ME application your approach is definitely wrong ;-). J2ME development will be one of the features of NetBeans IDE 4.0, but as it has not been open sourced yet, modules will be available when Beta1 is released == Aug/19. With J2ME MIDP project, you don't need to mount anything, classpath is taken from J2ME Wireless Toolkit or another emulator, build scripts use J2ME specific tasks for preverification, obfuscation, signing, execution, etc. Just wait two days. So I'm closing this bug as WONTFIX. Feel free to reopen if necessary.
closing