Situation:
1. You have some number of projects.
2. Some of these projects are libraries and described by Tools/Libraries.
3. There are also 3rd party libraries.
4. Project is big so many libraries are organized into packs: like CommonsLib that includes jars, source, javadoc for
commons-lang, commons-cli, commons-collections (from Apache Jakarta), etc.
5. Team works on same set of projects sharing part of netbeans profile: build.properties and descriptions of libraries
in xml.
6. One changes description of library in betbeans (like add commons-logging to CommonsLib) and share it's description
(build.properties and corresponded xml) together with all jars that belongs to it.
Problem is: project.properties isn`t updated.
Result: you can build projects that depends on such library in netbeans and you can build such projects using command
line and ant if you have same build.properties in home directory but you wouldn't be able to do so if you have outdated
build.properties in profile or don`t have it at all.
There are classpath properties for each library that project depends on in project.properties for purpose to build
project outside of netbeans enviroment. And these properties aren`t updated.
The only way to update these properties is:
1. go in project properties dialog
2. delete reference for library that was updated
3. click ok
4. again open project properties dialog
5. add again reference you deleted before
6. click ok
7. do 1-7 for every library that was updated
8. do 1-8 for every project you have
It would be great to have project properties work like build.xml and build-impl.xml. With latter recreated when it is
absent and refreshed when project properties are changed by configuration dialog. Another was is to refresh
# Property libs.XXXXX.classpath is set here just to make sharing of project simpler.
libs.XXXXX.classpath=...
lines in project properties. Perhaps refresh on Clean and Build (would be best) or at least on click at Ok button in
project properties dialog.