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 168159 - [67cat] JUnit Library lost
Summary: [67cat] JUnit Library lost
Status: RESOLVED DUPLICATE of bug 166585
Alias: None
Product: ide
Classification: Unclassified
Component: Import Settings (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: Jiri Skrivanek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-06 07:21 UTC by ulfzibis
Modified: 2009-09-22 09:41 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Missing JUnit (123.23 KB, image/png)
2009-07-06 07:22 UTC, ulfzibis
Details
logs (227.85 KB, application/x-compressed)
2009-07-06 07:43 UTC, ulfzibis
Details
build.properties (13.65 KB, text/plain)
2009-09-21 18:15 UTC, ulfzibis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ulfzibis 2009-07-06 07:21:41 UTC
[ BUILD # : 200906261401 ]
[ JDK VERSION : 1.6.* ]

See attachment.

I don't have any idea why. 1 day before all worked fine.
Comment 1 ulfzibis 2009-07-06 07:22:49 UTC
Created attachment 84388 [details]
Missing JUnit
Comment 2 ulfzibis 2009-07-06 07:43:52 UTC
Created attachment 84389 [details]
logs
Comment 3 ulfzibis 2009-07-06 08:37:03 UTC
Deleting cache didn't help.
Reverting project to old SVN state didn't help.
Renaming userdir helped.

Maybe you are interested on my old userdir (~50 MB)
Which part would be interesting ? (please don't say 'all')
Comment 4 Milos Kleint 2009-07-07 13:32:57 UTC
seems to be an instance of j2se project, reassigning. (could be also a generic java infrastructure issue)
Comment 5 Tomas Zezula 2009-09-02 16:06:15 UTC
Seems that the junit library is broken (the definition is broken).
No idea how this may happen (update, user edit, ....).
can you verify the content of nbuserdir/build.properties?
libs.junit.classpath
libs.junit_4.classpath
are the important properties.
Comment 6 Peter Pis 2009-09-17 15:28:23 UTC
Without requested information for long time - INVALID. We can't do anything in this case. Reporter, please add requested
information and reopen issue. Thanks in advance.
Comment 7 ulfzibis 2009-09-21 18:13:56 UTC
Sorry for delay (vacation) :-)
Luckily I have backup'd the userdir.
It seems, that junit paths have not been updated on import from 6.7RC3.
Comment 8 ulfzibis 2009-09-21 18:15:31 UTC
Created attachment 88041 [details]
build.properties
Comment 9 Tomas Zezula 2009-09-21 18:32:46 UTC
Thanks for the build.properties file.
It seems that the importer didn't correctly import the libraries (see the last attachment), there are libs pointing into the old NB installation which was probably 
deleted.
Comment 10 Jiri Skrivanek 2009-09-22 09:41:50 UTC
It is know issue 166585 that build.properties can be broken while importing settings. So far, you have to fix
libs.junit.classpath in build.properties manually. I also filed issue 172738 that classpath in Library Manager doesn't
corresponds to one in build.properties. That's why library is still showing under Test Libraries node.


*** This issue has been marked as a duplicate of 166585 ***