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 136224 - absolute paths in the projectproperties
Summary: absolute paths in the projectproperties
Status: RESOLVED WORKSFORME
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Milan Kubec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-01 07:47 UTC by christian255
Modified: 2008-10-15 14:47 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description christian255 2008-06-01 07:47:30 UTC
Hello,
Often I change projects between my desktop pc and my nootebook. On both pc the projects, the netbeans folder and the 
extenal frameworks (jar etc) are in the same folders but on different drives. If I copy the project, the links to the 
libraries are broken, because the linsk have absolute path. But there were different. Solution is to store the links 
to the libraries as relative path. I can change the path to relative only in the project.properties file. But this is 
not the way. To use a CVS is obsolete, because the project.properties file must also check in. Make a radiobutton in 
the dialog so that the user can choose the to store the data

Christian
Comment 1 Peter Pis 2008-06-01 08:57:08 UTC
And what about shared libraries? While creating a project in "Project" wizard there is "Using Dedicated Folder for
Storing Libraries" checkbox in 2nd step. Then just copy required libraries into "<lib>" folder and while adding them for
project via "Project Properties" use relative option.
Comment 2 christian255 2008-06-01 09:18:39 UTC
That is a solution, but not very good. With this solution all libraries where copy phyisicaly to the project. This is 
not good. 
If an update of one or more libraires is possible, all updatet libraries must copy into all projects.
A central management of 3party frameworks is not possible.
Comment 3 Tomas Danek 2008-08-26 10:44:27 UTC
well, i think that sharable libraries is the best solution. I do not understand why upgrading of one library means to
upgrade library of all projects - if you create libraries folder in e.g. C:\Libraries on your PC and Notebook, you can
import there all necessary library jars and *all* projects and utilize this one library storage.
Comment 4 Milan Kubec 2008-10-15 14:47:03 UTC
AFAICT there is nothing to be fixed, it can be solved by sharable libraries.