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 195368 - JUnit does not own modules/ext/junit-4.8.2.jar
Summary: JUnit does not own modules/ext/junit-4.8.2.jar
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: Jaroslav Tulach
Depends on:
Blocks: 195041
  Show dependency tree
Reported: 2011-02-11 22:51 UTC by Jaroslav Tulach
Modified: 2011-02-16 11:30 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Jaroslav Tulach 2011-02-11 22:51:01 UTC
There is some warning related to JUnit which breaks my build:

junit.framework.AssertionFailedError: NbModuleSuite has been started with failOnMessage(WARNING) and failOnException(INFO). The following failures have been captured:
[org.netbeans.core.startup.InstalledFileLocatorImpl] THREAD: main MSG: module org.netbeans.libs.junit4 in /home/hudson/.hudson/jobs/netbinox-sample/workspace/tmp/netbeans/platform does not own modules/ext/junit-4.8.2.jar at org.netbeans.LocaleVariants.findLogicalPath(

	at org.netbeans.junit.internal.NbModuleLogHandler.checkFailures(
	at org.netbeans.junit.NbModuleSuite$NbTestSuiteLogCheck.runTest(
	at org.netbeans.junit.NbModuleSuite$S.runInRuntimeContainer(
	at org.netbeans.junit.NbModuleSuite$
Comment 1 Jesse Glick 2011-02-11 23:07:42 UTC
<autoupdate> failed to write the correct entries to platform/update_tracking/org-netbeans-libs-junit4.xml. You can see this in nbbuild/build/test/unit/work/o.n.n.A/testDownloadAndExtractExternal/target/platform/update_tracking/org-netbeans-api-annotations-common.xml after running the test:

<file crc="1377266390" name="modules/org-netbeans-api-annotations-common.jar.external"/>

Here the name is wrong. (The CRC-32 does appear to match that of the actual file.)
Comment 2 Jaroslav Tulach 2011-02-12 07:19:49 UTC
I thought it will end up back on my plate. I hoped I did the right tricks with open/close the branch: core-main#7a8afa934fa9
Comment 3 Jesse Glick 2011-02-14 15:23:00 UTC
(In reply to comment #2)
> I hoped I did the right tricks with open/close the branch

Should be OK, but why did you reuse the branch at all? Could just have done the fix in trunk.
Comment 4 Jaroslav Tulach 2011-02-14 15:57:05 UTC
The fix logically belongs to the branch, it should have been there before the merge.

I am used to open branches which are merged into default. But that was before --close-branch become a mainstream. Next time I probably give up, as this does not worth the pain.
Comment 5 Quality Engineering 2011-02-16 11:30:03 UTC
Integrated into 'main-golden', will be available in build *201102160501* on (upload may still be in progress)
User: Jaroslav Tulach <>
Log: #195368: Remove .external from update_tracking file