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 48615 - AssertionError: Should have found an EXTERNAL URL matching nbfs://nbhost/SystemFileSystem/Templates/JUnit/
Summary: AssertionError: Should have found an EXTERNAL URL matching nbfs://nbhost/Syst...
Status: RESOLVED DUPLICATE of bug 48621
Alias: None
Product: java
Classification: Unclassified
Component: Classpath (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks: 41535
  Show dependency tree
 
Reported: 2004-09-07 22:08 UTC by Jesse Glick
Modified: 2004-09-08 16:08 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stack trace (1.70 KB, text/plain)
2004-09-07 22:08 UTC, Jesse Glick 		Details
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 2004-09-07 22:08:22 UTC 
Current sources. See stack trace. I was working
with the JUnit templates.
Comment 1 Jesse Glick 2004-09-07 22:08:45 UTC 
Created attachment 17448 [details]
Stack trace
Comment 2 Lukas Hasik 2004-09-08 15:03:11 UTC 
[200409071800 and ME]
probably when switching Platforms (i'm not sure). Users often switch
platforms in Mobility.
Comment 3 Jesse Glick 2004-09-08 15:14:23 UTC 
Did not involve switching platforms for me.

Just an effect of the fact that you have a Java source in the system
file system, and so it gets a ClassPath.SOURCE which is an SFS folder
(should be the root folder, in fact, if package declaration is
correct), and this is a valid classpath, but it has no EXTERNAL type
URL. I don't know why ClassPathSupport is even using URLMapper with
EXTERNAL; can simply use FileObject.getURL. (Already produces an
external URL where possible, anyway.) Of course javacore scanning will
need to know not to do anything with nbfs: URLs, but that is their
problem; nothing in the ClassPath API forbids it.
Comment 4 Tomas Zezula 2004-09-08 16:01:05 UTC 
Agree with Jesse, the issue is caused by parsing Templates on the
System Filesystem.
Comment 5 Jan Becicka 2004-09-08 16:08:47 UTC 

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