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.
Build: NetBeans IDE Dev (Build 200808260201) VM: Java HotSpot(TM) Client VM, 11.0-b12, Java(TM) SE Runtime Environment, 1.6.0_10-beta-b25 OS: Windows XP, 5.1, x86 User comments: STACKTRACE: (first 10 lines) Deployment error: The module has not been deployed. See the server log for details. at org.netbeans.modules.j2ee.deployment.devmodules.api.Deployment.deploy(Deployment.java:190) at org.netbeans.modules.maven.j2ee.ExecutionChecker.performDeploy(ExecutionChecker.java:86) at org.netbeans.modules.maven.j2ee.ExecutionChecker.executionResult(ExecutionChecker.java:62) at org.netbeans.modules.maven.execute.MavenJavaExecutor.run(MavenJavaExecutor.java:244) at org.netbeans.core.execution.RunClassThread.run(RunClassThread.java:151)
Please provide the server log, name and version of the server and (if possible) steps to reproduce.
Looks like something related to maven.
*** Issue 146314 has been marked as a duplicate of this issue. ***
maybe issue 143307 is related? http://hg.netbeans.org/main/rev/115665e34693
This issue has already 5 duplicates see http://statistics.netbeans.org/exceptions/detail.do?id=99155
Seems to be duplicate of issue 143307. *** This issue has been marked as a duplicate of 143307 ***
This was marked as a duplicate of 143307 which was fixed in August, but I am experiencing this exception in 200809140201 when I deploy to GlassFish and deployment fails. Spring is causing a deployment problem, and NetBeans puts up an exception window. When I fix the problem in Spring and GlassFish doesn't choke on it then no exception window in NetBeans. http://statistics.netbeans.org/analytics/detail.do?id=117110
ryan, it would be great if you had a sample project that demonstates the problem. I'm not seeing the exception that caused the deployment to fail in the log. I suppose it could be somehow logged at the wrong level that doesn't get noticed by the ui logger. It could be in the messages log though, or the build output. It's definitely not a duplicate of the original 143307 issue (but was assumed to be caused by the subsequent issue tracked as part of 143307 as well)