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 207956 - org.netbeans.api:org-netbeans-libs-junit4:RELEASE71 missing dep on junit:junit:4.10
Summary: org.netbeans.api:org-netbeans-libs-junit4:RELEASE71 missing dep on junit:juni...
Status: RESOLVED FIXED
Alias: None
Product: www
Classification: Unclassified
Component: Builds & Repositories (show other bugs)
Version: 7.1
Hardware: All All
: P2 normal (vote)
Assignee: pgebauer
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2012-01-31 15:44 UTC by Jesse Glick
Modified: 2012-06-12 16:24 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jesse Glick 2012-01-31 15:44:36 UTC 
libs.junit in RELEASE71-BETA [1] has a dependency on the external library junit:junit:4.8.2 as expected. Similarly, libs.lucene in RELEASE71 [2] depends on org.apache.lucene:lucene-core:3.0.3 as expected. Yet libs.junit in RELEASE71 [3] is missing a dependency on junit:junit:4.10 for some reason. The same in trunk [4] looks OK.

One practical impact is that nbm and nbm-application projects declaring a test-scoped dep on org.netbeans.api:org-netbeans-modules-nbjunit:RELEASE71 will not be able to run unit tests until a separate dep on junit:junit:4.10 is added.

The RELEASE71 artifacts, now released, cannot be retroactively fixed; but it may be possible to diagnose what went wrong and make sure it does not recur e.g. in RELEASE711. Possibly related to bug #195301 though that was fixed for RELEASE70 and this problem appeared in RELEASE71.

Note that in RELEASE71-BETA the *.jar manifest has "Maven-Class-Path: junit:junit:4.8.2" as expected, but this is missing in RELEASE71, meaning the external lib was somehow not detected... although it is not present in org.netbeans.external either (i.e. this is not bug #195300).

[1] http://bits.netbeans.org/maven2/org/netbeans/api/org-netbeans-libs-junit4/RELEASE71-BETA/org-netbeans-libs-junit4-RELEASE71-BETA.pom
[2] http://bits.netbeans.org/maven2/org/netbeans/api/org-netbeans-libs-lucene/RELEASE71/org-netbeans-libs-lucene-RELEASE71.pom
[3] http://bits.netbeans.org/maven2/org/netbeans/api/org-netbeans-libs-junit4/RELEASE71/org-netbeans-libs-junit4-RELEASE71.pom
[4] http://bits.netbeans.org/netbeans/trunk/maven-snapshot/org/netbeans/api/org-netbeans-libs-junit4/SNAPSHOT/org-netbeans-libs-junit4-20120126.193655-1.pom
Comment 1 Jesse Glick 2012-01-31 15:53:25 UTC 
Worked around in archetype in revision 15839.
Comment 2 pgebauer 2012-06-12 09:51:03 UTC 
Since a dependency exists for RELEASE72-BETA [1] and the build will be the same for 72beta and 72, I would say the issue has been fixed already. I will check the dependency once 72 maven repo is prepared for the release.


[1] http://bits.netbeans.org/maven2/org/netbeans/api/org-netbeans-libs-junit4/RELEASE72-BETA/org-netbeans-libs-junit4-RELEASE72-BETA.pom
Comment 3 Jesse Glick 2012-06-12 16:24:29 UTC 
And RELEASE711 and RELEASE712 were fine as well. Too bad it is unknown what went wrong in RELEASE71.