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.
"Allow build and deploy with errors" property is provided on project to build the project with errors. Even when "Allow build and deploy with errors" is checked build is failing.
I changed status to Invalid because of the project isn't specified (attached). I even didn't understand what project type is ment here. I change priority to P2 because of not all projects are built with error. I just have tried a synchronous sample project and it is built well.
Murali, please attach the project
Created attachment 43726 [details] project
project is attached. It is reporting errors due to another validation bug. As per the design of "Allow build and deploy with errors" user should be able build the project even there are valid bugs.
It is required for running driver projects. These driver projects are used by runtime for testing runtime regressions
I have investigated the problem and came to a decision that this issue is associated with the issue #100036. I have found the piece of code which cause the error. It is here: package org.netbeans.modules.bpel.project.anttasks; public class IDEValidateBPELProject private void processBpelFile(File file) throws BuildException { ... for (BPELFile bpel : myBPELFiles) { if (bpel.getTargetNamespace().equals(targetNamespace)) { throw new BuildException( " \n" + "BPEL files " + bpel.getName() + " and " + current.getName() + "\n" + "have the same target name space: " + targetNamespace + " \n \n" ); } } ... But I'm not confident about what to do with it. Also I have found another code, which looks very similar to the mentioned above: package org.netbeans.modules.bpel.model.validation.project; public class Validator This code looks a bit better (at least because of I18N in error message) but it isn't called at all. I don't know why. So it looks like a code duplication. I think it should be resolved anyway. I suggest to reassign this issue to the original author - Vladimir Yaroslavskiy
Fixed.
verified in Build 200709040000