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.
I just reprojectized my project and the new project was created with absolute paths in nbproject/configurations.xml. This removes any possibility of using this project in other locations or machines! This is a serious regression from past releases!
Make sure 'Path Mode' in Tools|Options|C/C++|Projects is set to Always Relative. I just tried creating a simple unmanaged project (is that what you call 'reprojectized'?) and don't see any absolute paths. I tried both Automatic and Custom modes. What part of configuration.xml contains absolute paths? Can you please attach that part to this bug report?
> Make sure 'Path Mode' in Tools|Options|C/C++|Projects is set to Always > Relative. I used a brand new userdir (and Path Mode defaults to Relative). > I just tried creating a simple unmanaged project (is that what you call > 'reprojectized'?) and don't see any absolute paths. I tried both Automatic and > Custom modes. I took my app (currently 2 netbeans projects with a 3rd acting as kind of a top-level project (similar to how a module suite manages individual modules). I stripped all of the nbproject directories because of several hundred code model errors (the phantom syntax error problem I emailed you about last week) and created 3 new projects. > What part of configuration.xml contains absolute paths? Can you please attach > that part to this bug report? Unfortunately, I was in experimentation mode and didn't pay enough attention to what I was doing. What I do remember is that I created the top-level project first. I added 20+ include directories (gnome/gtk spreads the includes over a *huge* number of directories) and built the product using my own Makefile (which calls autoconf-generated Makefiles). I then edited many of the problem sources (ie, the ones which showed many phantom syntax errors) and that problem had gone away. But a single project wouldn't deal with multiple binaries, so I created the 2nd project. I think I used automatic code assistance configuration for this project, as it doesn't require the gnome/gtk include stuff the 2nd program requires to build. That project's configuration.xml file ended up with about 30+ absolute paths (including project location). I hand edited the file and didn't keep a copy of the original, so I can't give you more details. I've done this excercise a 2nd time trying to duplicate the problem (of course it worked fine, this time :-). I'll try again and see if I can do it with the absolute paths in the project data...
Gordon, could you attach fragment of configurations.xml file with absolute paths? It would be nice if you provide us additional information: - path to nbproject - path to sources - example of object file that has wrong absolute path in configuration. Thanks, Alexander
I'll try to reproduce this on my Linux box. QA is encouraged to try it as well. If we all, including Gordon, can't reproduce it, then I'm going to downgrade the bug and not make it a showstopper.
I experimented with Freeway, and could get absolute paths with File Path Mode set to "Auto" or "Always Absolute", but not with "Always Relative". So everything went as expected.
I have not faced with any troubles while moving litesql-0.3.5 from Linux to Solaris using RC1 candidate build. Gordon, please reopen the bug if you are able to reproduce it once again.