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 72183 - Assertion error in SingleModuleProperties.refresh(SingleModuleProperties.java:176)
Summary: Assertion error in SingleModuleProperties.refresh(SingleModuleProperties.java...
Status: VERIFIED WORKSFORME
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Martin Krauskopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-02 16:26 UTC by Tomas Danek
Modified: 2006-04-06 12:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
AE (2.90 KB, text/plain)
2006-02-02 16:27 UTC, Tomas Danek
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Danek 2006-02-02 16:26:33 UTC
5.5 20060131 + enterprise pack

Assertion error while opening module properties.
However, seems to me like issue 72173  - random.
Comment 1 Tomas Danek 2006-02-02 16:27:33 UTC
Created attachment 28722 [details]
AE
Comment 2 Tomas Danek 2006-02-02 16:32:21 UTC
hard to say if reproducible in standalone 5.5 (random), i din't see it there.
Comment 3 Tomas Danek 2006-02-02 16:50:42 UTC
just reproduced in 5.5 standalone. Cleared s.w.
Comment 4 Jesse Glick 2006-02-02 18:06:13 UTC
The stack trace does not correspond to a trunk build. No steps to reproduce.
Comment 5 Tomas Danek 2006-02-03 13:04:00 UTC
This was reported against netbeans 5.5 (javaee5 branch - it was branched from
5.0) Please revert back version, 5.5 is intentional.Thx.
Comment 6 Jesse Glick 2006-02-03 14:01:41 UTC
assert getSuiteDirectory() != null;

Possibly related to usage of 5.5 platform? Not clear to me.
Comment 7 Tomas Danek 2006-02-03 14:22:36 UTC
QE uses ent_pack s.w. if issue is reproducible *only* in 5.5 with JSE clusters
and not in 5.5 itself.
Comment 8 Martin Krauskopf 2006-02-03 14:33:57 UTC
Not sure about TM.
Comment 9 Martin Krauskopf 2006-02-03 16:00:35 UTC
This issue is really unreproducible (by me and also by Tomas). Maybe that module
from dev build was manipulated in 5.0 based branch. Also Tomas said that it was
reproducible with the culprit module everytime. But module was unfortunately
lost so it cannot be checked now. If it can be reproduced again Tomas will keep
the module so we can analyze it. Until then works for me.
BTW this case is tested by SuitePropertiesTest.testMoveSubModuleBetweenSuites()
- Tomas told me that it happened to him after moving a suitecomponent from
another suite (but not sure about IDE from which it originated)
PS: I passed test on javaee5
Comment 10 Tomas Danek 2006-02-07 11:47:33 UTC
I'm pretty sure i reproduced with 5.5 preview module, however, you're right, i
was not able to reproduce, so i'll leave as worksforme.. I won't probably test
5.5 preview anymore.
Comment 11 Tomas Danek 2006-04-06 12:11:16 UTC
verified. If someone spots this problem, feel free to reopen.