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.
When building a module, the dependencies should be based on the updates installed in a user's home directory. I discovered this after installing 7.4 patch 1. I have a module which needs to use a non-API module. I have it added to my list of dependencies using the implementation version. However, after patch 1, I could build my module, but not install it. After some sleuthing thanks to some assistance on the NB dev mailing list, I found out that when I built my module, it used the supporting module version in the Program Files\Netbeans directory. However, when I installed my module, it was comparing it to newer supporting module version in my home directory. It should have had the dependency as 201311191022, and not as 201310111528 The NBM I created for my module has: Info / info.xml org.netbeans.modules.versioning.util = 201310111528. Looking at NetBeans 7.4/ide/modules/org-netbeans-modules-versioning-util.jar: OpenIDE-Module-Implementation-Version: 201310111528 However, I have another org-netbeans-modules-versioning-util.jar in my personal ...\AppData\Roaming\NetBeans\7.4\modules directory OpenIDE-Module-Implementation-Version: 201311191022 Mailing list thread: Problems with module after 7.4 patch 1
I deleted the modules directory from my home directory and then installed the updates, forcing them to install in the shared directories. That solved my issue. In general, it should taken the home directory versions into consideration. Possibly, the default for the update center is to install them into shared directories. However, I need to run NB as administrator to install them there...not something I generally bother to do. Fortunately I am able to run things with administrator privileges. If my computer was more locked down than it is, I would not have been able to do that and I would have been stuck.
Martin, wontfix I guess.
I hope this gets fixed. It is not easy to diagnose and, as I mentioned, if the computer is "secured", then it can create a situation that leaves a developer with no alternatives. Another question: Would this also mean that modules installed later would be inaccessible? For example, if I just downloaded the JavaSE version of Netbeans and then installed the JavaEE modules manually, would I not be able to use them creating a custom module? I would imagine I could if I downloaded the EE version of Netbeans to begin with, but if modules installed afterwards are not recognized, then this would be another blocking situation.
Sorry but WONTFIX. It would be quite hard to implement such that in build scripts would be classpath composed from application folder and user dir.
Would you consider detecting this condition and reporting something more helpful back to the user? I had no idea what was going on. "You have module updates installed in your user directory that are required for your module. Modules are built using only the modules in the shared directories. To continue development, you will need to re-install Netbeans and then install the updates into the shared directories. This may require running Netbeans as an Administator."