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.
Create a java project in NB,and create a folder named "lib" under the project directory.Put a jar file in the lib folder,and add it as a class libary for the project.Then copy the project directory to another computer,and open it in the IDE. NB will report a problem of "referenced library can not be found". Although this problem can be fixed by a wizard, I still think this is problem. here are followings: (1)if a jar file is stored in a sub folder of the project directory, it should be refered with a path info relative to the project folder; (2)if a jar file is stored in a folder out of the project directory, it should be refered with a absolute path info. The problem is that IDE always use a absolute path info,this is not convenient for project management.
I've thought it is fixed by shared libraries, I've tried it in current build and it doesn't work, indeed it behaves even worse as before, but it should be easy to fix. Steps to reproduce: 1) Create project with shared libs 2) Rename project using Rename project action (also rename project dir) 3) Project is marked as broken, and you cannot fix it since the list of libs is empty. The reason is that the project.xml/project/configuration/libraries/definition still points to the original (already deleted) project. The ProjectOperations should fix this reference after move to point to the new location.
moving opened issues from TM <= 6.1 to TM=Dev
I can't believe this won't be fixed in 6.1 final! This makes NB 6.1 very difficult to use in a shared environment (multiple developers using same project, project is in Subversion). This worked very good in NB 6.0! So, this is a regression! When I open a 6.0 project with RELATIVE paths to JARs in a lib folder, NB 6.0 displays full absolute path in the project properties dialog. NB 6.1 RC1 displays half of the JARs with full path and the other half with "lib/JAR-name". Then, when I add a new JAR from the lib folder, it adds the absolute path to project.properties. In this case, NB 6.0 always added the relative path to project properties. So, there are 2 issues, one cosmetic and one fatal.
Could someone responsible please raise the priority? Thanks!
I'm also experiencing this problem. Every time I edit JAR references in my projects Libraries the absolute paths are set in the project.properties instead of relative paths. This worked fine in NB 6.0. PLEASE raise the priority.
please consider converting your 6.0 projects to projects with "shared libraries".
OK, this seems to work fine. Still, the project is then again incompatible to the previous version.
>the project is then again incompatible to the previous version. NetBeans introduced the shared libraries to solve the problem with libraries sharing (http://wiki.netbeans.org/OutOfBoxVersionabilityProposal). The solution should be backward compatible with the old (<6.1) projects. By incompatible you mean that it define the project libraries as sharable then it doesn't work in 6.0?
I was guessing that, because all the project files were different after the change.
lhasik: the issue is different. in 6.0 and previous versions nbproject/project.properties *always* contained a relative path to jars, even for ridiculous paths like ../../../../../Program Files/NetBeans/... Then the private, non shared nbproject/private/private.properties hold the absolute path to the file, eg C:/Program Files/Netbeans/... in 6.1 we no longer bother maintaining the private.properties files with absolute paths. The idea was that if you don't care, you use the non-shared projects and therefore get the absolute paths everywhere straightaway. if you care, you use the shared libraries that manage the paths. if you use the shared libraries, you get different build script, changes in the project.xml and in both shared and non-shared cases the property values are written differently. That can indeed be considered incompatible change. However unlike in javacode APIs, it's rather tough to do any changes to the build process in a "compatible way"
*** Issue 133794 has been marked as a duplicate of this issue. ***
I think we've addressed this in another issue for 6.1 patches. Even if the project is not a "project with sharable libraries folder" we allow the user to pick how the jar file added to project shall be referenced. The choice is "absolute path", "relative path" and since 6.5 also "path from variable". For projects with sharable libraries folder we also offer to copy the jar to the libraries folder to keep external dependencies in one place. I consider the issue fixed.