[
http://jira.codehaus.org/browse/NMAVEN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129197#action_129197
]
Leopoldo Agdeppa III commented on NMAVEN-106:
---------------------------------------------
for the output pane, it won't be much of a problem since we could get it from
System.Diagnostics.Process#StandardOutput, we could also get the Input if need
in the future. without any complexity
and as for the NMaven and Maven Initializations, I think its tolerable enough
compared to waiting for the service embedder to start and keeping it running
while editing codes in VS and not using any maven commands yet.
I think maven embedder is good when you are using java based IDE, but in case
of VS, we can just make use of mvn command called directly in VS without
going through extra costs.
this approach will be more maintainable in future features since we will be
only maintaining a command string...
I will try to do some beach marks for this first :)
> 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
