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 253870 - Removing JUnit libraries does not resolve the "Hamcrest binaries missing" problem
Summary: Removing JUnit libraries does not resolve the "Hamcrest binaries missing" pro...
Status: RESOLVED WORKSFORME
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 8.1
Hardware: PC Windows 10 x64
: P3 normal (vote)
Assignee: Theofanis Oikonomou
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-27 15:31 UTC by mclaborn
Modified: 2017-04-28 03:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mclaborn 2015-07-27 15:31:59 UTC
For a project that includes JUnit, upgrading from 8.0.2 to 8.1 will produce the "Hamcrest binaries missing" project problem.  For some projects, I want to resolve this by removing JUnit from the project rather than adding the Hamcrest library. 

Doing so does not resolve the reference problem until the project is closed and reopened.
Comment 1 Theofanis Oikonomou 2015-09-17 12:39:29 UTC
Well when you open the project the project problem will be there. It cannot be updated unless you close and reopen your project. You can click the resolve button which will add the hamcrest library to your project and then remove which ever lib you wish. Would that work for you? Thank you
Comment 2 mclaborn 2015-09-17 13:56:46 UTC
This seems like more of a workaround than a solution.
Comment 3 Theofanis Oikonomou 2015-09-17 16:12:05 UTC
Well, when a project is opened and ide finds that it contains junit library and in order for the project to continue to work it needs to also include hamcrest library then this is offered to the user as a on-time one-button thing.

I think you would agree with me that there is no way on earth I could magically assume that the user might want to remove junit library when he opens the project when he already has set a dependency for junit, right?

That said I think this is really a rare corner case that I cannot cover. There is indeed a workaround as you mention and not a fix. A fix cannot be implemented in this case. I hope that it is not causing too much trouble. Thank you for reporting.