please define "log" to the output window.. no output is shown whatsoever? please attach the IDE log file.

Created attachment 139124 [details]
ide log file

The only thing logged to output window is

cd C:\development\Test; JAVA_HOME=C:\\tools\\Java\\jdk1.7.0_25 "\"C:\\tools\\NetBeans 7.3.1\\java\\maven\\bin\\mvn.bat\"" clean install

please check http://wiki.netbeans.org/FaqLogMessagesFile for log file of the IDE, what you attached is an installer log, sorry for not pointing you to the page in the first place.

this could be related to issue 228901. On windows since 1.7_21, executing external commands with space in path and space in parameters is intentionally broken on windows (security issues). We have a fix for 7.4 in which we use the path suggested by jdk team, convert the cmd line to cmd /c execution.

can you try either installing netbeans in a path without spaces (same goes for external maven installations and possibly also project sources) or downgrade to earlier jdk.

Alternatively please try downloading the 7.4 beta.

Created attachment 139132 [details]
ide log file

I tried netbeans 7.4 and logging to output window works with maven 3.

(In reply to toddjspin from comment #6)
> I tried netbeans 7.4 and logging to output window works with maven 3.

@Milos: So this issue can be resolved as won't fix (or something similar). Does this problem deserve a note in the system requirements doc of 7.4?

(In reply to markiewb from comment #7)
> (In reply to toddjspin from comment #6)
> > I tried netbeans 7.4 and logging to output window works with maven 3.
> 
> @Milos: So this issue can be resolved as won't fix (or something similar).
> Does this problem deserve a note in the system requirements doc of 7.4?

I'm not sure, it differs from the other reports that got a stacktrace in messages log. Also I'm a bit confused by the 2.x maven working claim.

toddjspin: is the IDE log file coming from the same IDE instance that ran the maven build and is it coming from same IDE session (after the maven build was executed)? if this were duplicate of issue 228901, I would expect the exception to show up in the log. 

is both maven3 and maven2 in your case installled in a place without space in path?

please reopen with the additional information. thanks.

Created attachment 139248 [details]
log file with netbeans installed at C:\tools\NetBeans7.3.1

I attached log file from this morning opening Netbeans 7.3.1....then executing clean and build on project. First maven 2.2.1 was selected...then I switched to the bundled maven and tried clean and build...then switched to maven 3.1. Only the maven 2.2.1 showed in output window.

Maven is installed in following locations.
M2
C:\tools\apache-maven-2.2.1
M3
C:\tools\apache-maven-3.1.0

(In reply to toddjspin from comment #11)
> I attached log file from this morning opening Netbeans 7.3.1....then
> executing clean and build on project. First maven 2.2.1 was selected...then
> I switched to the bundled maven and tried clean and build...then switched to
> maven 3.1. Only the maven 2.2.1 showed in output window.

was the log file attached before or after running the builds? from your description I read it was done before, but that's not helping much as any possible exceptions would only be printed during the maven build execution.

It was attached after.

(In reply to toddjspin from comment #13)
> It was attached after.

(In reply to toddjspin from comment #10)
> Created attachment 139248 [details]
> log file with netbeans installed at C:\tools\NetBeans7.3.1

Thanks. Nothing in the log that would link it with issue 228901. I suppose it's different. Nb in path with spaces is apparently not the cause here. Similar the space in path for maven.

by any chance fo you have anything defined in your MAVEN_OPTS environment variable or the Tools/Options/Maven global settings?
I'm basically after this cmd line switch that could somehow be executed by maven from the IDE:
-l,--log-file <arg>                    Log file to where all build output
                                        will go.

No I have nothing defined for those.

(In reply to toddjspin from comment #15)
> No I have nothing defined for those.

hmm.. I was betting on that as that's how I was able to reproduce.

(In reply to Milos Kleint from comment #16)
> (In reply to toddjspin from comment #15)
> > No I have nothing defined for those.
> 
> hmm.. I was betting on that as that's how I was able to reproduce.

what about the -q option somehow slipping in? (however the effect of this switch is more or less equal for 2.x and 3.x) only surefire plugin output was then printed for me then.

I'm wondering if the build is actually running for you or just somehow the IDE code hangs before executing. Do the Rerun and Stop related actions change enablement state? could you try starting up VisualVM to see if the Maven build shows up in the list of java files. Do a thread dump from maven jvm and also the IDE jvm.. I admit I'm clueless here..

I'm not sure if I did things correctly but I ran visualvm and clicked on thread dump for netbeans during the build and then for the maven process that showed up.

Created attachment 139304 [details]
netbeans thread dump

Created attachment 139305 [details]
maven thread dump

(In reply to toddjspin from comment #19)
> I'm not sure if I did things correctly but I ran visualvm and clicked on
> thread dump for netbeans during the build and then for the maven process
> that showed up.

To clarify...ran clean and build from ide...then in visualvm did thread dump for maven process...then ran clean and build again and did thread dump on netbeans process.

nothing relevant in the thread dumps unfortunately. The maven jvm seems to be happily progressing the build, while the nb JVM is waiting for output to show up. It's not possible to tell if the waiting is indefinite or just temporary.

closing as worksforme, in 7.4 working for both me and the reporter.
if you find steps to reproduce on any computer, please reopen.