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.
After NetBeans 4.0 beta2 build 200409220845 Generated my project, it also generated the build-impl.xml file (as expected). When clicking rebuild (or build) from the project, an error occures during the building process. The code compiles fine but the actual building of the 'jar' file in dist fails. (Compiling using java 1.5) The error is in the "j2seproject" tag. build-impl.xml:511: The <http://www.netbeans.org/ns/j2se-project/1:jar> type doesn't support the "name" attribute. BUILD FAILED (total time: 5 seconds) Removing the "Name" attribute from the tag results in another error. "Manifest is invalid: Manifest sections should start with a "Name" attribute and not "X- COMMENT"" Here is the appropriate XML section that fails (the second tag is the erroneous one, j2seproject) <target name="-do-jar-with-mainclass" depends="init,compile,-pre-pre-jar,-pre-jar" if="manifest.available+main.class"> <j2seproject:jar Name="MyProject.jar" manifest="${manifest.file}" xmlns:j2seproject="http://www.netbeans.org/ns/j2s e-project/1"> <manifest xmlns="http://www.netbeans.org/ns/j2se- project/1"> <attribute j2seproject:name="Main-Class" value="${main.class}"/> </manifest> </j2seproject:jar> </target>
Created attachment 18941 [details] My Build.xml file
I've never seen this before. The 'Name="MyProject.jar"' should not be there! How could it get there is not clear to me but if it was reproducible then any project would be affected and we would get such a bug report sooner. So I guess it must be result of something special in your configuration. Removing such an attribute makes build successful. The second error you mentioned is caused by the content of your manifest file which is unknown to me. Please provide detailed steps how to reproduce, on which JDK. Could you also try different JDK? Feel free to reopen with more info. Milan, could you please try to reproduce it too? Thanks.
I will try to reproduce that as soon as there is any clue how. Have never seen it.
Based on info send to me privately I still cannot say what might be the problem. Leaving RESOLVED. Please, if you encounter the problem again reopen the issue and explain steps you did and possibly describe your environment.