You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@maven.apache.org by bo...@werken.com on 2003/02/05 13:37:08 UTC

[maven-bug] Assigned: (MAVEN-255) maven.username does NOT necessarily need to be set

Message:

   The following issue has been re-assigned.

   Assignee: Ben Walding (mailto:jakarta@walding.com)
---------------------------------------------------------------------
View the issue:

  http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-255


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

     Status: Assigned
   Priority: Trivial

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: maven
  Component: None

   Assignee: Ben Walding
   Reporter: Ben Walding

    Created: Wed, 5 Feb 2003 6:09 AM
    Updated: Wed, 5 Feb 2003 6: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.werken.com/Administrators.jspa

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