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.
Summary: | AssertionFailedException: The application has not been initialized - need for default startlevel | ||
---|---|---|---|
Product: | platform | Reporter: | javydreamercsw <javydreamercsw> |
Component: | Netigso | Assignee: | Jaroslav Tulach <jtulach> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | akochnev, anebuzelsky, apireviews, darkos, exceptions_reporter, hbblcg, jglick, jrechtacek, mmirilovic, rkubacki |
Priority: | P1 | Keywords: | API_REVIEW_FAST |
Version: | 7.1 | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | 182835 |
Bug Depends on: | 205653 | ||
Bug Blocks: | 206347 | ||
Attachments: |
stacktrace
Hotfix, but the value "4" should be pluggable somehow Branding token to specify default bundle start level |
Description
javydreamercsw
2011-11-11 22:07:10 UTC
Created attachment 113137 [details]
stacktrace
was able to reproduce with NetBeans IDE Dev (Build 20111114-95ee7eead146) (#95ee7eead146) - just download the jira plugin from UC and since that moment the exception is thrown on each nb start - the plugin itself seems to work fine jarda - any chance this has something to do with the fix in issue #203790 p2 -> really visible. If this is not pointing to serious problem, I guess this gets "fixed" at least by turning off AE in FCS, right? Yes, it is very likely related to bug 204513. Since then all OSGi bundles in NetBeans have a startup level (by default 4). The level is specified inside of config/Modules/*.xml file. Probably the JIRA plugin has not been rebuild since then and has no startlevel specification (defaults to 1). If so, then the JIRA bundle gets activated sooner than rest of Eclipse runtime. Just rebuild JIRA, verify startlevel is there and if so, increase the spec version. Btw. for a rant about OSGi startlevels see: http://wiki.apidesign.org/wiki/OSGi > Just rebuild JIRA, verify startlevel is there and if so, increase the spec
> version.
osgi bundles are on the UC like jar files. autoupdate has to take care of that
Is it clear who will be fixing this? (In reply to comment #6) > Is it clear who will be fixing this? Jardo, Tomas told me you have promised to fix it. Is it true? I need to find out the code that generates config/Modules/*.xml file for downloaded bundles and modify it to include <startlevel>4</startlevel> to be aligned with changes made while fixing bug 203790. Created attachment 113444 [details]
Hotfix, but the value "4" should be pluggable somehow
On a second thought, it may be better to fix this directly in module system. Created attachment 113447 [details]
Branding token to specify default bundle start level
After this change we need to override the startlevel in projectized.xml no longer. Default level of "4" will be read during runtime from the branded bundle.
I'd like to integrate tomorrow.
(In reply to comment #3) > I guess this gets "fixed" at least by turning off AE in FCS, right? I doubt it - the stack trace in comment #0 does not look like a regular Java assertion, so it may not be affected by -ea/-da. (In reply to comment #4) > for a rant about OSGi startlevels see: http://wiki.apidesign.org/wiki/OSGi I think this is a bit off the mark. Seems like Eclipse is not really using OSGi as designed. Proper OSGi bundles are (acc. to spec) supposed to work regardless of what other bundles have or have not been started; that is why dynamic services exist, and why bundles are not started in topological order. In other words, we are working around misdesign in Eclipse, not OSGi per se. The problem presumably does not affect Eclipse and its RCP apps because they are not attempting to load code from an arbitrary compliant OSGi container, and so can make assumptions about runtime behavior not guaranteed by the spec. As for the diff in comment #11, it seems fine to me; basically the same as JG02 in bug #203790 comment #10. Given there is overall agreement I've integrated the change as ergonomics#dac9621ee0fb verified. IDE is started after installing JIRA without exception. The fix has not yet propagated from ergonomics to main-silver. Delaying integration. changeset: 634e004b4241 branch: release71 tag: tip parent: 20f16ed85a54 parent: fa77bc381037 user: Jaroslav Tulach <jtulach@netbeans.org> date: Mon Nov 28 14:58:16 2011 +0100 summary: Merge of #205019 to release71 branch Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/dac9621ee0fb User: Jaroslav Tulach <jtulach@netbeans.org> Log: #205019: Default bundle level can be assigned during runtime Integrated into 'releases' Changeset: http://hg.netbeans.org/releases/rev/dac9621ee0fb User: Jaroslav Tulach <jtulach@netbeans.org> Log: #205019: Default bundle level can be assigned during runtime *** Bug 205747 has been marked as a duplicate of this bug. *** verified in rc2 *** Bug 205916 has been marked as a duplicate of this bug. *** *** Bug 206192 has been marked as a duplicate of this bug. *** *** Bug 206211 has been marked as a duplicate of this bug. *** *** Bug 255691 has been marked as a duplicate of this bug. *** |