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.
Doesn't seem to do so anymore, regardless of the checkbox. Seems it was broken before - always built them - but then build-impl.xsl corrected a typo on May 31: - <xsl:attribute name="unless">${no.dependencies}</xsl:attribute> + <xsl:attribute name="unless">no.dependencies</xsl:attribute> which had the effect of exposing the underlying bug: setting no.dependencies to *any* value (even false!) makes the target be skipped. Ant treats any value for a property as true for purposes of if, unless, etc. Need to use <condition> and <istrue> to let the property be set to 'true' or 'false' and handle that appropriately.
Bug in j2seproject, but should check web/project too.
Yeah, I know about the behaviour of unless/if. It is broken only for newly created projects because mistakenly the property is set to "false". When changing this option the property is correctly set to true or removed from project.properties. I fixed this be removing property from project generator. src/org/netbeans/modules/java/j2seproject/J2SEProjectGenerator.java; new revision: 1.12; previous revision: 1.11
Wouldn't it be better to use <istrue> so you could override this setting in either direction (e.g. from the command line)? Not a priority really.
I wanted to move as much conditional logic to Java as possible and keep Ant script cleaner. But I consider command line ability to override building of subprojects important. Opening this issue for myself to fix that.
Original regression was fixed. Also not a blocker.
Fixed as part of other changes in build-impl.xml.