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.
Found using JavaCAPS R6U1 build 20081103-0628. JavaCAPS R6U1 installer build contains IEP. Uninstalled IEP nbm/plugins and then tried to install files from soarelease build081103_6. I observed that the IEP plugins are not really installed. They do not appear in the Plugin dialog's Installed tab, yet they seem to have been installed from the Downloaded tab. Even after restarting Netbeans and going through the download/install process again, the plugins are not showing up. I am not able to continue using IEP. Steps to reproduce: a. uninstall IEP plugins from Installed tab (IEP Engine, Help Topics, Project and Samples) b. follow prompt to restart Netbeans c. from Downloaded tab click Add Plugins, add IEP nbm files, then hit Install button As a result, the IEP nbm files seem to have been installed, but I do not see them in the Installed tab's list of plugins. d. repeat the process to install IEP nbm files and I get the same result. I will attach messages.log from one test. Below is an excerpt from the log of another test. WARNING [org.openide.filesystems.Ordering]: Found same position 1000 for both Templates/Project/SOA and Templates/Project/Samples INFO [org.netbeans.modules.autoupdate.services.InstallSupportImpl]: Timeout waiting for loading module org.netbeans.modules.iep.editor/1.0
Created attachment 73342 [details] messages.log
The issue exist, I see similar behaviour when installing bpel related modules and installing new bpel nbms. For iep related modules after step (d), if user restarts netbeans then iep editor related modules get installed correctly. so restart is a work around.
correct last comment: The issue exist, I see similar behaviour when uninstalling bpel related modules and installing new bpel nbms. ( similar behaviour exists when following the steps mentioned for bpel related modules.) For iep related modules after step (d), if user restarts netbeans then iep editor related modules get installed correctly. so restart is a work around.
The reason why we can not install latest nbms (both iep and bpel and I am sure others may fail) could be due to way installer installs initially set of modules. If we can install iep or bpel nbms on top of netbeans 61 patch4 then this will prove that something wrong is happening when we create installer. I am going to try iep nbm on netbeans patch4 http://smetiste.czech.sun.com/builds/netbeans/6.1/fixes/patch4/zip/ and see what happens.
Just verified that iep nbms can be installed and uninstalled repeatedly without any problems on netbeans patch4 from http://smetiste.czech.sun.com/builds/netbeans/6.1/fixes/patch4/zip/ So it seems like an environment problems once an installer is created using this netbeans patch4, we are not able to consistently install newer iep nbms (and not at all install newer bpel nbms) on javacaps u1 builds. One other thing I have noticed is that to install iep nbms on top of netbeans patch4 we need to install other relevant nbms: org-netbeans-modules-print01.nbm org-netbeans-modules-soa-ui01.nbm org-netbeans-modules-xml-search01.nbm org-netbeans-modules-soa-validation01.nbm which is fine but what I have noticed is that when we uninstall only 4 iep nbms not above 4 and try to reinstall 4 iep nbms, it require us to reinstall above 4 nbms as well, even though they are already installed, which is weird. In summary the upgrading of iep nbm on top of java caps 6 u1 is not an iep nbm upgrade problem, because on plain netbeans patch4 it works fine. it seems that after we create installer, some environment issue is preventing upgrading of iep nbms. Same happens for bpel nbms.
Created attachment 73842 [details] adding email thread: Vladimir tried to reprouduce this
see attached mail. Vladimir also tried to reproduce, and conclusion is as follows: "upgrading of newer iep nbm or bpel nbms on top of java caps 6 u1 requires restart of netbeans" ATTENTION DOC: Please add this to the readme. Downgrading this to p3.
Will the fix for this issue be that user is prompted or forced to restart NB after upgrading newer IEP nbms? Similar to how user is forced to restart NB when IEP plugins/nbms are uninstalled?