This issue was reported manually by jskrivanek.
It already has 2 duplicates
Build: NetBeans IDE Dev (Build 20120821-a6df67629e37)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.2-b09, Java(TM) SE Runtime Environment, 1.7.0_06-b24
OS: Windows 7
jskrivanek: To reproduce:
- open jellytools.java project in NetBeans
- open "Functional Test Packages|Examples|EmptyTest.java"
- run test (Ctrl+F6)
jskrivanek: Running UI test from IDE.
org.osgi.framework.BundleException: The bundle "org.springframework.web_3.1.1.RELEASE " could not be resolved. Reason: Missing Constraint: Import-Package: org.aopalliance.aop; version="[1.0.0,2.0.0)"
Created attachment 123402 [details]
Use NbModuleSuite.Configuration.honorAutoloadEager as shown in patch http://bugzilla-attachments-210618.netbeans.org/bugzilla/attachment.cgi?id=123408
or convince connected developers to fix dependency of this bundle.
I really don't want to edit every single test to add honorAutoloadEager(true) to NbModuleSuite configuration. Please, remove this bundle from IDE if it is not usable or catch this exception somewhere.
Your current test configuration (without honorAutoloadEager) differs from the standard netbeans.exe configuration. Should your goal be to mimic the standard configuration in the test run as closely as possible, then you find a way to modify your tests to include honorAutoloadEager(true).
Btw. is not there a protected static factory method in JellyTestCase that majority of test runs is using? In such case it would be enough to modify that method.
If standard netbeans.exe configuration corresponds to honorAutoloadEager(true) than it should be default value of NbModuleSuite.Configuration. Why not to change it there?
JellyTestCase has some utility method but in most cases we use directly NbModuleSuite.Configuration because we aggregate tests into suites (e.g. JellytoolsJavaSuite.java).
This bug already has 5 duplicates
Integrated into 'main-golden', will be available in build *201209130001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
User: Jiri Skrivanek <firstname.lastname@example.org>
Log: #217226 - Added honorAutoloadEager(true) to JellyTestCase.createModuleTest and to new method JellyTestCase.emptyConfiguration(). It should satisfy that IDE is run as close as possible to execution from command line.
Created attachment 124835 [details]
Started nb72 in fresh userdir.
Created attachment 124897 [details]
got this error after uninstalling the JIRA plugin
Created attachment 125196 [details]
Created attachment 126237 [details]
I was doing the review of this tutorial:
The error appearead at the point 6: Switch back to the Projects window, right-click the module, and choose Run.
Created attachment 126921 [details]
uninstalled "User installed plugins" - i think CVS, JIRA, HTML 5 whatever
Created attachment 126934 [details]
100 % reproducible for upgrade from NB 7.3 Beta to Beta 2
Created attachment 127024 [details]
just unistalled JIRA from beta2 build
Created attachment 127029 [details]
beta->beta2 (after upgrade on start)
removing 73beta2-stopper, since majority of reports were not relevant to this case and are separated now.
almost all reports from this issue are unrelated to the orignal report by jskrivanek. even if the stacktrace is the same, the error msg is different and indicates a different dependency problem.
the only reason for this one is the missing org.aopalliance.aop library
filed a new issue #221608 to cover all the other reports
should be gone since #a96c8a09ce3d