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.
1. Run IDE after (removing old userdir). 2. Create a Web app using visual JSF framework (for deploying to JEE 5 on Glassfish). 3. Open nbproject/project.properties file. 4. Examine the properties beginning with libs; they have hard-coded paths refering to specific installation of Netbeans. Problem has been there for at least 2 weeks. (See visualweb/samples/webapps/TravelCenter/nbproject/project.properties file for an example. This problem does not occur if simple JSF framework is chosen (second choice in New Project Wiz, second panel). Have seen this on two separate Windows machine and one Linux box.
Created attachment 47226 [details] project.properties file from simple web app.
> Examine the properties beginning with libs; they have hard-coded paths refering to specific installation of Netbeans It refers relatively to the jars, from which the library is composed. In 5.5 it was written in the private folder. You can see it in all project types if you add a library.
Your attachment is not good to read! (XML Parsing Error: not well-formed) It is not a P1 bug (even not a bug). These definition won't make the project bad. See the comment: # The library definition has always preference over this property. It is a library backup path that will even make the project more robust! Though not good for your sample project. Your specific workaround is, you can still manually remove these part for release purpose. It may be a new NetBeans feature, if so, I will make it INVALID. If not, I will reassign to NetBeans project. Tomas Zezula wrote: > Unfortunately I don't know much about this feature, I will need to find > out the commit log and corresponding issue to find out > what was the motivation, it's related to the headless build improvements > in NB 6.0. I will let you know during the weekend. > Petr Pisl wrote: >> Hi Po-Ting, >> >> I have asked to Tomas Zezula and I'm waiting for his response. But >> from my point of view the bug is invalid. Other projects have the same >> behavior. I think that this is a feature not a bug. It's strange that >> you are not able to reproduce. Could you send me a your >> project.properties file. >> >> Petr
Not a bug, it's a NetBeans feature. If you don't agree with this feature, then you should propose and ask the J2SE project module for more enhancement! Tomas Zezula wrote: > I looked into the j2seproject. The code doing the library relativization > is pretty old, it purpose is to make the sharing and the headless build > more simpler. > When the whole library (all files form classpath volume) is collocated > to the project, the relative paths are stored into the > project.properties. The intention is > that the project.properties has lower priority than the > build.properties, so when the library exists in the library manager, the > library from the library manager is taken, > if not the (headless) build can use the relativized property from the > project.properties, so when the project was correctly shared it's buildable. > > Diff of change introducing the relativization: > http://deadlock.netbeans.org/fisheye/browse/netbeans/java/j2seproject/src/org/netbeans/modules/java/j2seproject/ui/customizer/J2SEProjectProperties.java?r1=1.6&r2=1.7
I still think it's a bug. If you need to store invalid, relative paths which are ignored by the IDE when a project is loaded why not store them in the nbproject/private/private.properties file? Isn't that what it's for? I suppose I will just set the paths to some other information like the URL to this issue. ;)
I didn't say it's a good feature. If you don't like this NetBeans feature, you should file bug against J2SE project module. It controls all project types, not just web project or visualweb framework. > Not a bug, it's a NetBeans feature. If you don't agree with this feature, then you should propose and ask the J2SE project module for more enhancement!
BTW, since this new feature does not break any functionality; everything is still working and even more robust. You should not file P1 or even P2 for this issue.
The reason I filed it is because: if you create a project and later open it with a different version of the IDE (with different versions of the libraries, etc.), your project is still pointing at the older libraries and not the newer ones (in the currently running version of the IDE). I think I will log it as an issue against J2SE as you suggested. Thanks.