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 255140 - Fix for "Hamcrest binaries missing" (Junit) not persistent
Summary: Fix for "Hamcrest binaries missing" (Junit) not persistent
Status: RESOLVED INVALID
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 8.1
Hardware: PC Linux
: P3 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-09-09 14:23 UTC by mclaborn
Modified: 2015-09-10 19:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (125.66 KB, text/plain)
2015-09-09 14:23 UTC, mclaborn 		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 mclaborn 2015-09-09 14:23:50 UTC 
Product Version = NetBeans IDE Dev (Build 201509080002)
Operating System = Linux version 3.13.0-63-generic running on amd64
Java; VM; Vendor = 1.8.0_51
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.51-b03

Reproducibility: Happens every time

In this build of NetBeans, every time I start up NetBeans, I get the "Hamcrest binaries missing" error for 2 of my projects.  Every time, I do the Resolve step, but next time I start NB, the error shows up again.
Comment 1 mclaborn 2015-09-09 14:23:54 UTC 
Created attachment 156017 [details]
IDE log
Comment 2 Jiri Kovalsky 2015-09-09 22:05:02 UTC 
Reassigned for further evaluation.
Comment 3 Theofanis Oikonomou 2015-09-10 07:48:01 UTC 
From the log file I see that org.netbeans.libs.junit4 module, which bundles junit and hamcrest jars, is enabled. I did not spot any relevant exception. Please reopen giving some more info like project type and test libraries previously registered by your project. Also, ideally attaching a sample project that has this behavior of not persisting the modified set of test dependencies. Thank you for reporting.
Comment 4 mclaborn 2015-09-10 19:27:01 UTC 
I figured out what was causing this: When I first started testing 8.1 beta, I created an empty "hamcrest" user library in my 8.0 installation so that I would not have a bunch of problems switching back to 8.0 with my existing projects.

When I started testing this dev build, the config migration process included that "hamcrest" library and it was conflicting somehow with the real one provided in 8.1.  When I removed that empty library, this problem went away.