You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Shane Isbell (JIRA)" <ji...@codehaus.org> on 2008/03/31 06:20:58 UTC
[jira] Commented: (NMAVEN-106) NMaven Service Embedder vs Simple
Call of mvn.bat using dotnet System.Diagnostics.Process
[ http://jira.codehaus.org/browse/NMAVEN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129191#action_129191 ]
Shane Isbell commented on NMAVEN-106:
-------------------------------------
One of the primary reasons for hosting the service on Jetty is for performance. By running NMaven continually in a long running process, you get the advantage of JIT optimizations, as well as one time startup costs of both Maven and NMaven. Also keep in mind that the VS output pane needs to read in the Maven console output, so a socket connection needs to be established between the VS and the embedder. If you run NMaven through System.Diagnostics.Process then you take the hit everytime you build the project.
I think it would be possible to add an additional SOAP command that would directly stop the embedder.
> NMaven Service Embedder vs Simple Call of mvn.bat using dotnet System.Diagnostics.Process
> -----------------------------------------------------------------------------------------
>
> Key: NMAVEN-106
> URL: http://jira.codehaus.org/browse/NMAVEN-106
> Project: NMaven
> Issue Type: Improvement
> Affects Versions: 0.14 (Unreleased)
> Environment: win32
> Reporter: Leopoldo Agdeppa III
>
> the Current way of running nmaven in Visual Studio is through NMaven Service Embedder running on Jetty
> and commands are given through SOAP requests, then the service embedder executes the maven command using
> embedded maven
> One problem on this approach is canceling an executed nmaven command in VS
> I think using this approach is not too maintainable since you have to maintain to components
> One solution is to use System.Diagnostics.Process in VS for running maven commands since mvn.bat is already adequate for running nmaven commands
> in this way we only have to maintain the command executed in the process
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira