You are viewing a plain text version of this content. The canonical link for it is here.
Posted to npanday-commits@incubator.apache.org by "Paul G (JIRA)" <ji...@apache.org> on 2010/12/01 16:53:10 UTC
[jira] Created: (NPANDAY-357) Add 'deploy' option to 'Current
NPanday Project' menu options
Add 'deploy' option to 'Current NPanday Project' menu options
-------------------------------------------------------------
Key: NPANDAY-357
URL: https://issues.apache.org/jira/browse/NPANDAY-357
Project: NPanday
Issue Type: Improvement
Components: Visual Studio Add-in
Affects Versions: 1.2.1
Environment: Windows
Reporter: Paul G
When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty.
It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-357) Add 'deploy' option to 'Current
NPanday Project' menu options
Posted by "Brett Porter (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965912#action_12965912 ]
Brett Porter commented on NPANDAY-357:
--------------------------------------
as with the others, if you can supply a patch of the change that you made, we'd be happy to apply it!
> Add 'deploy' option to 'Current NPanday Project' menu options
> -------------------------------------------------------------
>
> Key: NPANDAY-357
> URL: https://issues.apache.org/jira/browse/NPANDAY-357
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Affects Versions: 1.2.1
> Environment: Windows
> Reporter: Paul G
>
> When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty.
> It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-357) Add 'deploy' option to 'Current
NPanday Project' menu options
Posted by "Adelita L. Padilla (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971613#action_12971613 ]
Adelita L. Padilla commented on NPANDAY-357:
--------------------------------------------
Hi Paul G,
We've tried and tested your patch and it works fine.
Applied it in r1049474
Thanks!
> Add 'deploy' option to 'Current NPanday Project' menu options
> -------------------------------------------------------------
>
> Key: NPANDAY-357
> URL: https://issues.apache.org/jira/browse/NPANDAY-357
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Affects Versions: 1.2.1
> Environment: Windows
> Reporter: Paul G
> Fix For: 1.3-incubating
>
> Attachments: NPANDAY-357.patch
>
>
> When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty.
> It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-357) Add 'deploy' option to 'Current
NPanday Project' menu options
Posted by "Adelita L. Padilla (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adelita L. Padilla resolved NPANDAY-357.
----------------------------------------
Resolution: Fixed
Fix Version/s: 1.3-incubating
> Add 'deploy' option to 'Current NPanday Project' menu options
> -------------------------------------------------------------
>
> Key: NPANDAY-357
> URL: https://issues.apache.org/jira/browse/NPANDAY-357
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Affects Versions: 1.2.1
> Environment: Windows
> Reporter: Paul G
> Fix For: 1.3-incubating
>
> Attachments: NPANDAY-357.patch
>
>
> When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty.
> It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-357) Add 'deploy' option to 'Current
NPanday Project' menu options
Posted by "Paul G (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul G updated NPANDAY-357:
---------------------------
Attachment: NPANDAY-357.patch
Patch added as requested
> Add 'deploy' option to 'Current NPanday Project' menu options
> -------------------------------------------------------------
>
> Key: NPANDAY-357
> URL: https://issues.apache.org/jira/browse/NPANDAY-357
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Affects Versions: 1.2.1
> Environment: Windows
> Reporter: Paul G
> Attachments: NPANDAY-357.patch
>
>
> When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty.
> It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-357) Add 'deploy' option to 'Current
NPanday Project' menu options
Posted by "Joe Ocaba (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966377#action_12966377 ]
Joe Ocaba commented on NPANDAY-357:
-----------------------------------
Thanks Paul, We will try out your patch and apply it after testing.
> Add 'deploy' option to 'Current NPanday Project' menu options
> -------------------------------------------------------------
>
> Key: NPANDAY-357
> URL: https://issues.apache.org/jira/browse/NPANDAY-357
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
> Affects Versions: 1.2.1
> Environment: Windows
> Reporter: Paul G
> Attachments: NPANDAY-357.patch
>
>
> When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty.
> It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.