[
http://jira.codehaus.org/browse/NMAVEN-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leopoldo Agdeppa III updated NMAVEN-106:
----------------------------------------
Attachment: NMAVEN-106.patch
just a little change for ChangeMavenSettingsXmlForm.SettingsXmlFile == null
to run with -s option if its not null
> 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
> Assignee: Brett Porter
> Fix For: 0.14 (Unreleased)
>
> Attachments: NMAVEN-106.patch, nmaven-106.patch, NMAVEN-106.patch,
> vsaddin_fix.zip
>
>
> 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
