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 58127 - [41cat] Wrong compile status badge on J2ME project
Summary: [41cat] Wrong compile status badge on J2ME project
Status: CLOSED FIXED
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P2 blocker (vote)
Assignee: Adam Sotona
URL:
Keywords:
Depends on:
Blocks: 58342
  Show dependency tree
 
Reported: 2005-04-20 23:42 UTC by ulfzibis
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
log file (25.53 KB, text/plain)
2005-04-21 01:41 UTC, ulfzibis 		Details
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 ulfzibis 2005-04-20 23:42:44 UTC 
[ BUILD # : last Q-build ]
[ JDK VERSION : 1.5.0_02 ]

When changing something in a Java document and saving it, the compile status badge doesn't appear. After undoing the change, the compile status badge appears weather the class file is again valid. Also after 'Build Main Project' the compile status badge remains.
Also VCS status indicator is wrong. See Issue 58124.
Comment 1 ulfzibis 2005-04-21 01:41:06 UTC 
Created attachment 21784 [details]
log file
Comment 2 Adam Sotona 2005-04-21 15:30:13 UTC 
reassigning
Comment 3 Adam Sotona 2005-04-21 15:31:08 UTC 
fixed in trunk
Comment 4 ulfzibis 2005-04-21 20:51:15 UTC 
What does this mean: "fixed in trunk" ?
Comment 5 Lukas Hasik 2005-04-22 11:15:06 UTC 
definitelly not P1, decreasing priority to P3.  
<br>I'm sorry but we are in High Resistance mode and this issue won't get into
mobility pack for NB4.1
<br>
Fixed in trunk means that it's fixed for NB4.2 release now.
Comment 6 ulfzibis 2005-04-22 19:19:41 UTC 
Not to have the overview, if compile was *successful or not* is only P3.

I don't agree with this !!!
Comment 7 Lukas Hasik 2005-04-26 15:41:54 UTC 
increasing priority, this bug will be fixed for 4.1 -> P2

Adam, when you'll commit the fix into release4.1 branch change the 'Target
milestone' to 4.1, please.

There remains only minor issue 58342.
Comment 8 Adam Sotona 2005-05-03 17:37:18 UTC 
correcting target milestone