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 http://services.netbeans.org/synergy/client/app/index.html#/assignment/139/v/1 Create Enterprise Application Test Case Steps Go to main menu File > New Project In New Project wizard select Maven > Maven Enterprise Application and push Next Type EntAppPrj to the Project Name field and push Next Push Finish Expected result: Four projects are created (ear,ejb,pom and war), the output contains message about "BUILD SUCCESS".There's missing dependencies warning icon in Projects tab. Check that it can be resolved using "Show and resolve problem" action from context menu. Actual result: Four projects are created (ear,ejb,pom and war), the output contains message about "BUILD SUCCESS".There's NO missing dependencies warning icon in Projects tab. Testcase needs an update? Product Version: NetBeans IDE 8.0 Beta (Build 201401091443) Java: 1.7.0_45; Java HotSpot(TM) 64-Bit Server VM 24.45-b08 Runtime: Java(TM) SE Runtime Environment 1.7.0_45-b18 System: Windows 7 version 6.1 running on amd64; Cp1252; en_US (nb)
One of the projects created is now "web" instead of "war".
i'm not sure if anything changed, but one possible explanation for "no warning" is that one chooses maven coordinates that were chosen before test:test for example. If these were built before, they are in local repository and the warning will not show. Assuming the warning is about missing dependency.
could be related to issue 237428, right now I cannot really see that the behaviour is broken nor can I find in what way has it changed.
1. http://hg.netbeans.org/main-golden/rev/3d7198ee62eb introduced missingNonSibling variable in ProblemReporterImpl.doArtifactChecks. and condition "missingNonSibling ? ProblemReport.SEVERITY_MEDIUM : ProblemReport.SEVERITY_LOW" on the severity of the problem. SEVERITY_LOW is important here since problems with that severity didn't mark the project as "broken". I'm not entirely sure what missingNonSibling is effectively doing but that's for a different discussion I guess. At the very least the behaviour is very contextual. 2. http://hg.netbeans.org/core-main/rev/27a7af56deb8 introduces the bridging to ProjectProblemsProvider new API. In here, there's only error/warning levels for problems. Apparently we converted MEDIUM and LOW to be warning. So with this changeset the warning started appearing more frequently. 3. http://hg.netbeans.org/core-main/rev/21b46b6dc148 finishes the conversion to ProjectProblemsProvider avoiding the old ProblemReporter api altogether. In here we ship creation of SEVERITY_LOW problems in doArtifactChecks() method. That's the primary cause for disappearance of the warning icon badge. So effectively the warning started showing in this case in 7.4 and now disappeared. I would argue that the disappearing is correct. One reason is that it was not showing before either but more importantly since 7.4 we've got Compile on Save turned on for all projects by default. And when running we are linking the target/classes directories of these projects together. So effectively for running/debugging a project with dependency projects opened, these don't have to be in local repository in most cases. Of course there are cases when the build *will* fail because of missing dependency in local repo but I suppose we can live with that. please update testspec