|
 FAQ-O-Matic : JBuilder 5 Known Bugs :
Sometimes, import package.* statements seem to be ignored. JBuilder's compiler says the classes within such packages can not be found when they are referenced. If the import statements are changed from a package (wildcard) import to a set of class imports, the errors disappear. |
| This is a known bug. It does not happen under all conditions. If it does happen, workarounds are to expand the wildcard into a list of classes you actually used from the package, or to use explicit package.class naming in the source code.
Thus, import javax.swing.*; ... JFrame frame = new JFrame(); could be changed to one of the following forms:
import javax.swing.JFrame; ... JFrame frame = new JFrame();
import javax.swing.*; ... javax.swing.JFrame frame = new javax.swing.JFrame(); 2001-Sep-11 8:46am gyles19@visi.com | |
| [Append to This Answer] | |
| 2001-Sep-11 8:46am |
| Previous: |
 "Search | Find in Path" refuses to search for string "???" even if pattern matching is disabled. "Search | Find" does allow this to work.
|
| Next: |
JBuilder5 Memory Leak
|
| ||||||||
|
Java Community
Java Tools |
Code Central JB OpenTools |
Community Recent Threads |
Borland Chat Chat FAQ |
||||||||||||||
|
Feature Matrices 3.0 | 3.5 | 4.0 5.0 | 6.0 | 7.0 |
Shop for JBuilder |
JBuilder Downloads and reg keys |
Report Piracy | ||||||||||||||
|
Online Manuals 4.0 | 5.0 | 6.0 7.0 |
Borland DevSupport's Bug/RFE Form Quality Central Client |
JB Patches & Updates |
JBuilder FAQs TIs | ||||||||||||||
|
JBuilder Newsgroups |
Tamaracka's News Archive |
Mr. Haki's JBuilder Machine |
JGuru's JBuilder FAQ |
||||||||||||||
|
Sun's Bug Parade |
|||||||||||||||||
|
|||||||||||||||||
