The following comment has been added to this issue:
Author: Joerg Schaible
Created: Thu, 19 Aug 2004 6:36 AM
Body:
IMHO the port property just makes no sense for scpexe, since you cannot know what
option is used. For the internal handled protocols this should not be the problem.
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPARTIFACT-37?page=comments#action_23242
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-37
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPARTIFACT-37
Summary: ScpExeDeployer ignores the maven.repo.[name].port attribute
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-artifact-plugin
Assignee:
Reporter: Mark Church
Created: Mon, 2 Aug 2004 8:41 AM
Updated: Thu, 19 Aug 2004 6:36 AM
Environment: Fedora Core 2, J2SDK 1.4.2_05, Maven 1.0
Description:
The ScpExeDeployer does not honor the maven.repo.[name].port attribute if it is set.
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
