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.
Summary: | java.lang.IllegalArgumentException: URI scheme is not "file" | ||
---|---|---|---|
Product: | obsolete | Reporter: | schinni <schinni> |
Component: | visualweb | Assignee: | Winston Prakash <wjprakash> |
Status: | NEW --- | ||
Severity: | blocker | CC: | dkonecny, issues, jayashri, potingwu, wjprakash |
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
The Exception and the data that netbeans tried to send
The project Properties file |
Description
schinni
2008-04-22 06:27:33 UTC
Created attachment 60526 [details]
The Exception and the data that netbeans tried to send
Could you please attach your project to this issue? I cannot reproduce it without your project. Thanks! If your project is big or intellectual, please just attach your project's property file: nbproject/project.properties Thanks! Created attachment 60583 [details]
The project Properties file
Could you please try to remove all values under the following comments in your project.properties file: # Property libs.Commons.classpath is set here just to make sharing of project simpler. # The library definition has always preference over this property. ... Sometime these 'cache' do not work properly because they are not updated correctly. Do make a copy before removing them. If it's still not working, then restore it. I did as asked (modifying the project.properties file). However, the problem still remains. From the threads dump, looks like a general web project, or IDE project issue. Assign to web project for further investigation. I do not know how you ended up with your project in this state but looking at project.properties there seems to be jars referenced from two NetBeans installations: * E:\\Program Files\\NetBeans 6.1 RC2 * C:\\Program Files\\NetBeans 6.0.1 Could you open Tools->Libraries and scroll through all libraries you have there and check whether some of them is broken? Should be displayed in red. Fixing that should resolve also your project opening issue. If you know how to reproduce this problem would be great. I think it depends on the IDE libraries your project is using in NB 6.0. And it looks to me like one of them is not provided in NB 6.1? Is that possible? Thanks, -David I even tried creating a new project from scratch (using the existing sources option). However, when i was adding libraries to my project, i got this error again. Also, i was unable to open any jsp page for editing. At this point, i thought restarting netbeans might help. Upon restarting, netbeans gave me the same error again (URI scheme is not "file") and this time i saw it automatically remove the project i had created earlier from the projects pane. I tried this process three times - each time with the same result. Hence, we cannot develop at all using Netbeans 6.1 RC2. Please help... Response to david... All the libraries are ok. None is red. I am able to reproduce the problem on my pc. I will try and reproduce it on other pcs too. All the libraries that my project is using, are available. When I had created a new project and added all the libraries, there were no errors prompted. I was even able to compile the project successfully. However, I was unable to open any jsp page. It sort of hung. And as mentioned in my previous post, upon restarting the IDE, the IDE threw the URI scheme is not "file" error and removed the project from the Projects pane. Trying to add it back again results in the same problem. From the exception I can see where the problem is but I would like to figure out how to reproduce it. Two things I would like to ask you to try please: * I was not correct in my previous reply that broken library would be displayed in red. It is the jar of a library which is displayed in red if it cannot be translated to physical jar file on disk. Could you please go to Tools->Libraries again and select each library your project is using (or go through all of them if unsure) and when library is selected check that classpath list contains valid items - broken one should be displayed in red. If there is one fix it by removing broken library entry and adding correct one. * you said "I even tried creating a new project from scratch (using the existing sources option)" - this definitely should work. If first step does not help could you please try to start NB6.1RC2 with fresh userdir (e.g. netbeans --userdir /tmp/tmp-nb-userdir) and recreate the project again? Pay attention especially to all libraries you are going to use. The first step worked. I found that the Web UI components library was referencing dojo and scriptaculous which were missing. Upon removing them, i was able to load my project successfully. Thanks =). A point to note: It seems like we cannot have multiple versions of netbeans installed on the same system. I had version 6.0.1 on my system when i installed 6.1 RC2. Even uninstalling both and reinstalling only 6.1 RC2 hadn't helped reset this library. The manual update worked like a charm though. > The first step worked. I found that the Web UI components library was referencing dojo and scriptaculous which were
> missing. Upon removing them, i was able to load my project successfully. Thanks =).
I think Visual Web component may need to release note this issue, or describe the problem in details to see how the IDE
general project can automatically resolve this.
Visual Web QA may want to check whether this issue will always happen when multiple NetBeans versions coexist.
Re. "It seems like we cannot have multiple versions of netbeans installed on the same system" - it should work without problems. I still do not know how to reproduce your problem and without that it is difficult to fix it. Here is what I tried: Note: NB6.0.1 when installed and run on fresh computer will create IDE userdir directory <user-home>/.netbeans/6.0 . NB 6.1rc2 when started for the first time will check presence of "<user-home>/.netbeans/6.0" and will offer "import 6.0 settings?" and will create IDE userdir directory <user-home>/.netbeans/6.1rc2 . To try to reproduce the problem I did: * I removed <user-home>/.netbeans/6.0 and started NB6.0.1 and created Web Project with Visual JSF (that it project with Web UI Components library) and exited IDE * I removed <user-home>/.netbeans/6.1rc2 and started NB6.1rc2 and said "Yes" to import 6.0 settings Result of this was that project created in 6.0 was successfully opened in 6.1rc2 and I can see it's using "Web UI Components" library and that library was upgraded to 6.1rc2 version. So for me everything seems to be working fine. Btw. what you mean by "scriptaculous" - I'm not expert in Visual JSF but in 6.0 I did not have any scriptaculous.jar on classpath? The scriptaculous 1.5.0 jar was i think in the following location: NetBeans default installation directory\visualweb2\modules\ext\ With regards to the installation, I originally had netbeans 5.5 on my system. I had then uninstalled it and installed netbeans 6 last december. Upon the release of 6.0.1, i had installed 6.0.1 (i do not remember if i had uninstalled 6.0 or the 6.0.1 installation used the same folder). A week back, I had installed 6.1 RC2 and the problem i described earlier came about. Passing back to visualweb team. You guys know about changes of Web UI Components library so it should be easier for you to figure out scenario how to reproduce the problem. Knowing which users are really impacted (NB6 users? or NB5.5 users?) you can decide whether it is worth to mention this problem in Release Notes or not or do something else. The Web UI Components team should know better how the libraries have been changed and may need to release note about it. |