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.
NetBeans 5.x creates projects xml with nb-module-project/2 xml schema definition: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://www.netbeans.org/ns/project/1"> <type>org.netbeans.modules.apisupport.project</type> <configuration> <data xmlns="http://www.netbeans.org/ns/nb-module-project/2"> <code-name-base>org.yourorghere.module4</code-name-base> <standalone/> <module-dependencies/> <public-packages/> </data> </configuration> </project> I found these problems if projects created in NetBeans 5.x are used: 1) Add test dependency in NetBeans 6.1 by using UI. The schema nb-module-project/2 was not increased to nb-module-project/3. Exception will be thrown if you try to open it in NB65beta. 2) Try add test dependency in NetBeans 6.5 by using UI. Exception that schem is not valid is thrown. Less experienced NBM developers are lost :(.
Certainly #2 is a duplicate. Maybe too late for #1.
issue 143561 related..
As Jesse has written, #2 is a duplicity, I guess sustaining could solve #1 by back-porting the patch (?). Since this is P2, rising the priority of the original issue. *** This issue has been marked as a duplicate of 142594 ***
patch3 is the last patch planned for 6.1. After this one 6.5 should be out -> no more 61 patches but 65. Solution could be provide a patch (jar) attached to the issue.
Backporting the patch would anyway not help people who already added the test dep. Might be some way for ABPFS to automatically check whether a newer schema would fix the validation issue and silently upgrade in-memory. I will think about it.