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.
Created attachment 109180 [details] Screenshot of broken AnagramGame project opened right after 7.0 -> 7.0.1 upgrade. Product Version: NetBeans IDE 7.0 (Build 201104080000) Java: 1.7.0; Java HotSpot(TM) 64-Bit Server VM 21.0-b17 System: Linux version 2.6.35-22-generic running on amd64; UTF-8; cs_CZ (nb) Userdir: /home/cesilko/.netbeans/7.0 Description: ============ If user installed full distro of 7.0 and didn't activate any Java feature and then upgraded to 7.0.1 through NetBeans Update Center, it's not possible to open any Java projects then. See attached screenshot and list of upgraded modules. Right clicking project nodes offers only "Close" and "Resolve Problems..." popup menu actions. The latter only displays error dialog. Steps to reproduce: =================== 1. Launch full distribution of NetBeans IDE 7.0 with empty dialog. 2. Invoke "Tools > Plugins", switch to "Settings" tab and change URL of NetBeans Distribution Update Center [1]. 3. Switch to "Updates" tab and install both new Auto Update modules. 4. Restart the IDE and invoke "Tools > Plugins" again. 5. "Updates" tab will display all 7.0.1 modules that were changed since 7.0. Install them and after another restart open any already created Java application e.g. Anagram Game project. It will be broken. [1] http://updates.netbeans.org/netbeans/updates/7.0.1/uc/final/distribution/catalog.xml.gz
Created attachment 109181 [details] List of modules updated during 7.0 -> 7.0.1 full distro upgrade.
The error dialog displays this message: Not all requested modules can be enabled: [StandardModule:org.netbeans.modules.spring.beans jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-spring-beans.jar, StandardModule:org.netbeans.modules.maven.kit jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-maven-kit.jar, StandardModule:org.netbeans.modules.form.kit jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-form-kit.jar, StandardModule:org.netbeans.modules.hibernate jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-hibernate.jar, StandardModule:org.netbeans.modules.debugger.jpda.ui jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-debugger-jpda-ui.jar, StandardModule:org.netbeans.modules.java.kit jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-java-kit.jar, StandardModule:org.netbeans.modules.j2ee.persistence.kit jarFile: /home/cesilko/NetBeans/7.0/java/modules/org-netbeans-modules-j2ee-persistence-kit.jar]
Created attachment 109182 [details] Screenshot of modules to be updated when upgrading from 7.0 -> 7.0.1
This is serious, probably not so usual scenario but we need to know whether there are some other consequences.
Hi, I can confirm this problem on Windows XP 32b with Java Web Application (no frameworks, Glassfish 3.1, Java EE 6 Web) as well. There's no problem with PHP projects. Product Version: NetBeans IDE 7.0.1 RC1 (Build 201106222100) Java: 1.7.0; Java HotSpot(TM) Client VM 21.0-b17 System: Windows XP version 5.1 running on x86; Cp1252; en_US (nb)
Ok, so this is a stopper for NB 7.0.1 and needs to be fixed NOW! SO we will have time to test it for regressions as well as to confirm other scenarios.
I can confirm this scenario causes this problem. It's reproducible if and only if Java feature is not active. If Java feature is active, everything works correctly. So, it's not common way how to upgrade IDE, moreover if an user works with Java projects it's most likely the Java feature is active => minor scope user can be affected. Affected users can reinstall IDE by common way w/o lost any data. I suggest to decrease it and waive it for now.
Yet another important note, a possible fix of this problem won't solve it because the bug is in NB7.0(!) which handles update (not in NB701) to solve it we need a backport to NB7.0.
Reproduced with: Product Version: NetBeans IDE 7.0.1 RC1 (Build 201106222100) Java: 1.7.0; Java HotSpot(TM) Client VM 21.0-b16 System: Linux version 2.6.38-8-generic running on i386; UTF-8; en_US (nb) After upgrade I opened J2SE project with form. Not all requested modules can be enabled: [StandardModule:org.netbeans.modules.hibernate jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-hibernate.jar, StandardModule:org.netbeans.modules.debugger.jpda.ui jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-debugger-jpda-ui.jar, StandardModule:org.netbeans.modules.maven.kit jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-maven-kit.jar, StandardModule:org.netbeans.modules.j2ee.persistence.kit jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-j2ee-persistence-kit.jar, StandardModule:org.netbeans.modules.form.kit jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-form-kit.jar, StandardModule:org.netbeans.modules.java.kit jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-java-kit.jar, StandardModule:org.netbeans.modules.spring.beans jarFile: /home/tester/netbeans-7.0/java/modules/org-netbeans-modules-spring-beans.jar]
No disagreement with waiving this one on nbdev => seems approved.
*** Bug 200215 has been marked as a duplicate of this bug. ***
This is a stopper for NB 7.0.1, tzezula is working on the hot-fix for 701...
Created attachment 109545 [details] Patch file
The primary thing - e.g. compatible versioning is achieved. Manifest says: OpenIDE-Module: org.netbeans.modules.parsing.lucene and OpenIDE-Module-Specification-Version: 1.5.1 - this means ergonomics from 7.0.1 will not have problem to enable java cluster from 7.0. Will 7.0 code link against 7.0.1 parsing.lucene classes? I generated diff of final state of changed classes against release70_base and as far as I can tell, there are no new (abstract) methods in existing interfaces. Thus yes, I believe the code will link. The change seems to be suitable for 7.0.1 in my opinion. API side note: Rather than typing DocumentIndex.DocumentIndexWithStatus I'd prefer shorter DocumentIndex.WithStatus
Thanks Jardo for review. I've tried 7.0.1 parsing.lucene in 7.0 and it works fine. The name of inner interface is good enough for NB 7.0.1.
The patch works for me. I'm able to open Java project after upgrade 7.0 to 7.0.1 with the patched modules. Tomas, please push the patch into release701. Thanks a lot
Fixed http://hg.netbeans.org/releases/rev/de2f176fde98
Integrated into 'releases' Changeset: http://hg.netbeans.org/releases/rev/de2f176fde98 User: Tomas Zezula <tzezula@netbeans.org> Log: #199808:Broken projects after manual upgrade 7.0 -> 7.0.1 of not initialized full distro
*** Bug 200307 has been marked as a duplicate of this bug. ***
reopen - see issue 200307 ... also reported by Stepan Z. : the Lucene upgrade is offered after fresh 201107211357 installation and always breaks it
>Parsing Lucene Support [1.5.1 -> 2.2.1] From where the 2.2.1 comes from? The 1.5.1 is the new one and 2.2.1 is not a part of NB 7.0.1
Seems as Autoupdate issue (maybe only non updated catalog).
Petr, please evaluate ASAP - thanks in advance.
Ok, I think I found the reason ... running NB 7.0.1 shows registered UC as catalog : http://updates.netbeans.org/netbeans/updates/7.0.1/uc/final/distribution/catalog.xml.gz ... but this is a catalog from RC1 we published in June, not the one we recently build. The correct catalog is located on smetiste as http://smetiste.czech.sun.com/builds/netbeans/7.0.1/daily/2011-07-21_13-57-19/uc/catalog.xml So, Petr Gebauer could you please publish at 'uc' folder on updates.netbeans.org for us ?
The issue 200307 is not a duplicate of this issue. I've reopened it and closing this one.
*** Bug 200373 has been marked as a duplicate of this bug. ***
(In reply to comment #17) > Fixed http://hg.netbeans.org/releases/rev/de2f176fde98 How do I apply this fix?
If the NB is already broken I'am afraid you need to reinstall it.
I just downloaded the latest 7.0.1 installer from http://netbeans.org/downloads/ and the bug is still there. The problem is that projects that can be opened in 7.0.1RC1 release are not being opened in 7.0.1 release. Please provide instructions on how to apply the patch when this bug is closed. The only relevant warnings that I see in messages.log are: WARNING [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: No server descriptor found in J2EE/DeploymentPlugins/WebLogic9 WARNING [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: No server descriptor found in J2EE/DeploymentPlugins/Tomcat55 WARNING [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: No server descriptor found in J2EE/DeploymentPlugins/J2EE WARNING [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: No server descriptor found in J2EE/DeploymentPlugins/gfv3 WARNING [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: No server descriptor found in J2EE/DeploymentPlugins/gfv3ee6 WARNING [org.netbeans.modules.j2ee.deployment.impl.ServerRegistry]: No server descriptor found in J2EE/DeploymentPlugins/JBoss4
Alex, can you send me an example of such broken project _privately_ via e-mail (jkovalsky@netbeans.org)? What are exact steps to reproduce this bug? What is build number of the 7.0.1 RC you used to successfully open those projects? And which distribution of 7.0 did you download? JavaEE or All? I am downgrading this bug to P3, because we only guarantee import of settings between FCS releases and not milestone builds like Dev/Beta/RC.
It's not an individual project, but a project Group. I cannot send you the entire group of projects, but I can send you project configuration files if it helps. I see that there is a patch attached to this bug but I am not sure how to apply the patch. Could you provide any information on this?
Completely uninstalling 7.0.1rc1 and importing 6.9.1 project configurations worked for me. Importing 7.0.1rc1 project configurations in 7.0.1 is still not working.
The patch is just a source code diff. It was just for a reviewer. Thanks for your update. If you reproduce the bug during upgrade from 7.0 FCS to 7.0.1 FCS, don't hesitate to reopen this bug. Then the project configuration files would help. Thanks.
Was apparently FIXED before alecswan's updates, which probably belong in a separate report if reproducible.