[
http://jira.codehaus.org/browse/NMAVEN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129266#action_129266
]
Leopoldo Agdeppa III commented on NMAVEN-106:
---------------------------------------------
The Refactor came out well, and its build time is just the same as the soap
service, and has improved the performance, no more waiting for jetty to run,
and no more service running while not needed,
maven executions are sandboxed in a different process, this means no collision
when building many projects
> 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
