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.

Bug 61174 - Project classpath must be rescanned after changing J2ME configuration
Summary: Project classpath must be rescanned after changing J2ME configuration
Status: CLOSED FIXED
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: All All
: P3 blocker (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-20 14:04 UTC by hfmanson
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hfmanson 2005-07-20 14:04:58 UTC 
When I change the configuration of a J2ME project with different API's the
editor incorrectly reports errors. These errors disappear when I restart the IDE
because then the project classpath is rescanned. The project classpath scan
should also be executed when the J2ME configuration is changed.
Comment 1 Tomas Hurka 2005-07-20 14:11:26 UTC 
This has nothing to do with java/hints. Reassigning to classpath module, but probably this a J2ME 
problem, since changing Java platform works right.
Comment 2 Tomas Zezula 2005-07-20 14:57:15 UTC 
Tomas is right, it's a bug of J2ME. The J2ME ClassPathIml should update its
content and fireEvent after the configuration is changed.
Comment 3 Martin Ryzl 2005-07-20 15:08:26 UTC 
yes, it's a bug in Mobility Pack - alrady fixed, updated modules are to appear
on NetBeans update center soon.
Comment 4 Martin Ryzl 2005-08-10 13:42:39 UTC 
fixed - updated bits have been uploaded to the update center
Comment 5 Lukas Hasik 2006-01-17 13:57:43 UTC 
verifying all old issues