[jira] Closed: (MPDEPLOY-7) maven.username does NOT necessarily need to be set

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Fri, 25 Jun 2004 11:37 AM

not modifying legacy deploy method anymore
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPDEPLOY-7

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPDEPLOY-7
    Summary: maven.username does NOT necessarily need to be set
       Type: Improvement

     Status: Closed
   Priority: Trivial
 Resolution: WON'T FIX

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-deploy-plugin

   Assignee: 
   Reporter: Ben Walding

    Created: Wed, 5 Feb 2003 6:09 AM
    Updated: Fri, 25 Jun 2004 11:37 AM

Description:
There is no real reason that maven.username needs to be set for ssh deployments.

The file ~/.ssh/config is often used to store all the pertinent information for the connection. Including ports, user ids, keys, compression etc.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org