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 73833 - VerifyClassLinkage task loops until StackOverflow
Summary: VerifyClassLinkage task loops until StackOverflow
Status: VERIFIED FIXED
Alias: None
Product: apisupport
Classification: Unclassified
Component: Harness (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Jesse Glick
URL:
Keywords: REGRESSION, SIMPLEFIX
Depends on:
Blocks:
 
Reported: 2006-03-21 16:23 UTC by tschlegl
Modified: 2006-03-23 08:45 UTC (History)
2 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 tschlegl 2006-03-21 16:23:48 UTC 
I've got two jar packages together in a single library module each referencing
the other one in it's manifest. At build time i get a recursive looking at these
two jars until a StackOverflow when the verify-class-linkage task is executed.
Comment 1 Jesse Glick 2006-03-21 23:03:10 UTC 
Hmm, ought to be fixed, but I would anyway recommend you remove any Class-Path
from a JARs in a lib module. It will be ignored at runtime and so is potentially
misleading.
Comment 2 tschlegl 2006-03-22 08:31:41 UTC 
Unfortunately there are leagcy reasons to keep the classpath settings in the
manifests - the jars are also part of an application suite w/o netbeans platform.
Currently we removed the verify-class-linkage dependency at the "netbeans" target
of common.xml
Comment 3 Jesse Glick 2006-03-22 17:35:15 UTC 
Not sure whether P2 or P3 is more appropriate. Scary build error if it happens,
but fairly simple workaround once you know it. Not clear whether this kind of
situation is common in the field - are there many 3rd-party libs which have
cyclic deps in Class-Path like this?

Checking in VerifyClassLinkage.java;
/shared/data/ccvs/repository/nbbuild/antsrc/org/netbeans/nbbuild/VerifyClassLinkage.java,v
 <--  VerifyClassLinkage.java
new revision: 1.4; previous revision: 1.3
done
Comment 4 Jesse Glick 2006-03-22 17:40:46 UTC 
Petr says P2 it is, so merging. I did some sanity checking on a few examples but
verification would be appreciated.

Checking in VerifyClassLinkage.java;
/shared/data/ccvs/repository/nbbuild/antsrc/org/netbeans/nbbuild/VerifyClassLinkage.java,v
 <--  VerifyClassLinkage.java
new revision: 1.1.2.1; previous revision: 1.1
done
Comment 5 pzajac 2006-03-23 08:45:13 UTC 
Verified in 50u1 with two testcases:
1. 
dependencies
lib1 -> lib2
lib2 <- lib2

2.
dependencieas
lib1 -> lib2
lib2 -> lib3 
lib3 -> lib1

The second testcase I've already tested in runtime with simple module project.