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 "Adelita L. Padilla (JIRA)" <ji...@apache.org> on 2010/12/15 10:39:01 UTC

[jira] Resolved: (NPANDAY-357) Add 'deploy' option to 'Current NPanday Project' menu options

     [ 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.