You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/06/28 22:55:12 UTC

[jira] Created: (MPARTIFACT-22) New ScpExeDeployer

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPARTIFACT-22

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPARTIFACT-22
    Summary: New ScpExeDeployer
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-artifact-plugin

   Assignee: 
   Reporter: Leif Nelson

    Created: Mon, 28 Jun 2004 4:54 PM
    Updated: Mon, 28 Jun 2004 4:54 PM

Description:
I have implemented an ScpExeDeployer plugin (like I said I would back in November!).  When I upgraded to RC4, I saw that you were "serious" about getting rid of the old scp/ssh type of deployment. :-)  Anyways, I really need to have the ssh-agent type of support in the deployment artifacts, so I implemented this plugin.  It's backwards compatible with folks that supply the old maven.ssh.executable, maven.ssh.args, maven.scp.executable, maven.scp.args.  I also made it look for these params in "server-specific" props like you do with the new stuff..  maven.repo.x.ssh.executable, maven.repo.x.ssh.args, maven.repo.x.scp.executable, maven.repo.x.scp.args.  So, if someone wanted to deploy with different args, or different commands to different servers, the plugin would support that.

This work was done in regards to this email thread..  http://nagoya.apache.org/eyebrowse/ReadMsg?listName=users@maven.apache.org&msgNo=8065

Thanks much for consideration. :-)

--Leif


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

[jira] Updated: (MPARTIFACT-22) New ScpExeDeployer

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Leif Nelson (mailto:lnelson@mail.com)
       Date: Mon, 28 Jun 2004 4:55 PM
    Comment:
Here's the patch.
    Changes:
             Attachment changed to Artifact-ScpExeDeployer.patch
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPARTIFACT-22?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPARTIFACT-22

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPARTIFACT-22
    Summary: New ScpExeDeployer
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-artifact-plugin

   Assignee: 
   Reporter: Leif Nelson

    Created: Mon, 28 Jun 2004 4:54 PM
    Updated: Mon, 28 Jun 2004 4:55 PM

Description:
I have implemented an ScpExeDeployer plugin (like I said I would back in November!).  When I upgraded to RC4, I saw that you were "serious" about getting rid of the old scp/ssh type of deployment. :-)  Anyways, I really need to have the ssh-agent type of support in the deployment artifacts, so I implemented this plugin.  It's backwards compatible with folks that supply the old maven.ssh.executable, maven.ssh.args, maven.scp.executable, maven.scp.args.  I also made it look for these params in "server-specific" props like you do with the new stuff..  maven.repo.x.ssh.executable, maven.repo.x.ssh.args, maven.repo.x.scp.executable, maven.repo.x.scp.args.  So, if someone wanted to deploy with different args, or different commands to different servers, the plugin would support that.

This work was done in regards to this email thread..  http://nagoya.apache.org/eyebrowse/ReadMsg?listName=users@maven.apache.org&msgNo=8065

Thanks much for consideration. :-)

--Leif


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

[jira] Closed: (MPARTIFACT-22) New ScpExeDeployer

Posted by ji...@codehaus.org.
Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Tue, 6 Jul 2004 9:42 AM

applied - thanks. Please also attach docs to diff in future.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPARTIFACT-22

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPARTIFACT-22
    Summary: New ScpExeDeployer
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-artifact-plugin

   Assignee: Brett Porter
   Reporter: Leif Nelson

    Created: Mon, 28 Jun 2004 4:54 PM
    Updated: Tue, 6 Jul 2004 9:42 AM

Description:
I have implemented an ScpExeDeployer plugin (like I said I would back in November!).  When I upgraded to RC4, I saw that you were "serious" about getting rid of the old scp/ssh type of deployment. :-)  Anyways, I really need to have the ssh-agent type of support in the deployment artifacts, so I implemented this plugin.  It's backwards compatible with folks that supply the old maven.ssh.executable, maven.ssh.args, maven.scp.executable, maven.scp.args.  I also made it look for these params in "server-specific" props like you do with the new stuff..  maven.repo.x.ssh.executable, maven.repo.x.ssh.args, maven.repo.x.scp.executable, maven.repo.x.scp.args.  So, if someone wanted to deploy with different args, or different commands to different servers, the plugin would support that.

This work was done in regards to this email thread..  http://nagoya.apache.org/eyebrowse/ReadMsg?listName=users@maven.apache.org&msgNo=8065

Thanks much for consideration. :-)

--Leif


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