[jira] Created: (NMAVEN-137) Reference listing in VS remains after removing a NMaven artifact
Reference listing in VS remains after removing a NMaven artifact Key: NMAVEN-137 URL: http://jira.codehaus.org/browse/NMAVEN-137 Project: NMaven Issue Type: Bug Reporter: Leopoldo Agdeppa III When selecting 'Remove NMaven Artifact from the solution explorer menu; the reference is removed from the pom, but the listing remains in the solution explorer reference list. Environment: Maestro 1.5.1 server, NMaven 0.14-maestro-1.6-M1 client -- 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
[jira] Created: (NMAVEN-138) Code Signature not viewable from within Visual Studio
Code Signature not viewable from within Visual Studio - Key: NMAVEN-138 URL: http://jira.codehaus.org/browse/NMAVEN-138 Project: NMaven Issue Type: Bug Affects Versions: 0.14 (Unreleased) Reporter: Leopoldo Agdeppa III When signing the code using the procedures listed, these updates are not reflected in the IDE. Example, from solution explorer > Properties > Signing. The display for signature / keyfile is blank. Only the pom is updated in the signing by nmaven. It should also update the csproj / vbproj file such that it will reflect the changes in solution explorer > Properties > Signing -- 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
[jira] Updated: (NMAVEN-138) Code Signature not viewable from within Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leopoldo Agdeppa III updated NMAVEN-138: Attachment: screenshot-1.jpg screen shot > Code Signature not viewable from within Visual Studio > - > > Key: NMAVEN-138 > URL: http://jira.codehaus.org/browse/NMAVEN-138 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Attachments: screenshot-1.jpg > > > When signing the code using the procedures listed, these updates are not > reflected in the IDE. > Example, from solution explorer > Properties > Signing. The display for > signature / keyfile is blank. > Only the pom is updated in the signing by nmaven. It should also update the > csproj / vbproj file such that it will reflect the changes in solution > explorer > Properties > Signing -- 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
[jira] Updated: (NMAVEN-137) Reference listing in VS remains after removing a NMaven artifact
[ http://jira.codehaus.org/browse/NMAVEN-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leopoldo Agdeppa III updated NMAVEN-137: Attachment: NMAVEN-137.patch fix patch > Reference listing in VS remains after removing a NMaven artifact > > > Key: NMAVEN-137 > URL: http://jira.codehaus.org/browse/NMAVEN-137 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-137.patch > > > When selecting 'Remove NMaven Artifact from the solution explorer menu; the > reference is removed from the pom, but the listing remains in the solution > explorer reference list. -- 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
[jira] Updated: (NMAVEN-138) Code Signature not viewable from within Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leopoldo Agdeppa III updated NMAVEN-138: Attachment: NMAVEN-138.patch Fix Patch submitted, and an added GUI functionality for adding a keyfile in pom.xml in VS > Code Signature not viewable from within Visual Studio > - > > Key: NMAVEN-138 > URL: http://jira.codehaus.org/browse/NMAVEN-138 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.14 (Unreleased) >Reporter: Leopoldo Agdeppa III > Fix For: 0.14 (Unreleased) > > Attachments: NMAVEN-138.patch, screenshot-1.jpg > > > When signing the code using the procedures listed, these updates are not > reflected in the IDE. > Example, from solution explorer > Properties > Signing. The display for > signature / keyfile is blank. > Only the pom is updated in the signing by nmaven. It should also update the > csproj / vbproj file such that it will reflect the changes in solution > explorer > Properties > Signing -- 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
[jira] Created: (MNG-3042) Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project.
Extending a Mojo Class and used in a new Mojo Project, parameter fields in the parent mojo are not set, this disables reuse of existing mojo project. - Key: MNG-3042 URL: http://jira.codehaus.org/browse/MNG-3042 Project: Maven 2 Issue Type: Bug Components: Plugin API Reporter: Leopoldo Agdeppa III I have an Existing maven-plugin-a and I want to extend its functionality and put it in maven-plugin-b, so what i did is I put the the maven-plugin-a as a dependecy in maven-plugin-b and extended the mojo class from A, the issue on this is that paramter fields from A is not set, when I used plugin-B, I think this disables reusing and extending of mojos -- 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
[jira] Created: (NMAVEN-106) NMaven Service Embedder vs Simple Call of mvn.bat using dotnet System.Diagnostics.Process
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
[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=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
[jira] Issue Comment Edited: (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=129197#action_129197 ] lagdeppa edited comment on NMAVEN-106 at 3/31/08 2:48 AM: -- 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 benchmarks for this first :) was (Author: lagdeppa): 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
[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=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
[jira] Updated: (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:all-tabpanel ] Leopoldo Agdeppa III updated NMAVEN-106: Attachment: vsaddin_fix.zip Attached is a the re-factored code > 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 > Attachments: 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
