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.
This enhancements calls for an Update button in Project Properties > Libraries panel > Module Dependencies tab, whose associated action would update the selected module-dependencies to the version/implementation found in the current application/platform. The current way to do this is to manually remove the modules and add them back!
Generally you should not do this - at least not in the forward direction; you should only increment the version of a dependency when actually using a new API, and then only to the version mentioned in @since for that API. (There is some use case for attempting to decrement the version of a dependency when seeing if you can compile against an older platform, but I think this is relatively uncommon.) Anyway bug #70917 is more likely the preferred approach for Ant-based projects. For Maven-based projects the platform dependency is usually given by a global property anyway.
In my case scenario I want to synchronize a platform-based application to the latest release of NetBeans platform by updating all suite modules to the most recent NetBeans platform dependencies. Following a recent post by Geertjan, it seems that I an achieve this by running the "fix-dependencies" target in the build.xml of each of my modules. This should result in only incrementing not decrementing version, no?
(In reply to comment #2) > I want to synchronize a platform-based application to the > latest release of NetBeans platform by updating all suite modules to the most > recent NetBeans platform dependencies. You do not need to do this. If the modules run with the older platform, then they should run with the newer platform too. > I [can] achieve this by running the "fix-dependencies" target in the > build.xml of each of my modules. No, this is for something else - removing unused compile-time dependencies, similar to Maven's dependency:analyze.