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.
See diff. I assume Petr just used the GUI dialog to edit project.xml. But now <class-path-extension> is at the top, which is wrong - won't validate.
Not only that, it have also added artifical /1 to my org.openide.filesystems dependency, which made my module unavailable at runtime.
I have never known it to add a major release version without your instructions. Can you reproduce that?
I've also never noticed the case with an artifical major release version. Started for the rest....
Strange, I tried reproducing the problem by starting over from collab/output/nbproject/project.xml,v1.4 and unchecking/checking impl dependency on core/output2 and it generated the project.xml exactly the same as v1.8, that is, completly correct.
Well, WORKSFORME unless a test case can be found. BTW Martin it is a good idea in unit tests for the code that writes project.xml to validate against schema. Cf. dkonecny's tests for ant/freeform.
OK, works even for me now.
But the problem with class-path-extension is still there. Easily reproduced. 1) open j2eeserver/j2eeapis project 2) add some friend 3) xml becomes invalid I'll add a validation check to all ProjectXMLManager tests and fix this.
Starting... means also complete rewriting of the ProjectXMLManagerTest and also hopefully completely getting rid of example-external-projects - which can be deteled then. Or are they needed for something else Jesse? (I'll ensure that none of other tests are using them, ProjectXMLTest is the last heavily dependend test AFAIK)
Fixed. Checking in ProjectXMLManager.java; 1.37 --> 1.38 Checking in project/ProjectXMLManagerTest.java; 1.23 --> 1.24
v