Maven 2.x Stage Plugin

The stage plugin only supports copying from http(s) to scp urls

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-alpha-2
  • Fix Version/s: 1.0-alpha-2
  • Labels:
    None
  • Number of attachments :
    1

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. MSTAGE-6 stage:copy fails with Maven 2.0.9

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Bug - A problem which impairs or prevents the functions of the product. MSTAGE-5 support non-command execution wagons for deployment

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Bug - A problem which impairs or prevents the functions of the product. MNG-3581 stage:copy ClassCastException with maven 2.0.9

  • Blocker - Blocks development and/or testing work, production could not run
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

New Feature - A new feature of the product, which has yet to be developed. WAGON-209 Extend Wagon API to support the Stage Plugin

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Rahul Akolkar added a comment -

I discovered this in trying to move a staged release today.

The attached patch fixes it for me (I used scpexe:// for the target repo, which fails without the patch and succeeds with the patch). The earlier cast to ScpWagon for the lines in question seems overly restrictive and exclusionary.

Show
Rahul Akolkar added a comment - I discovered this in trying to move a staged release today. The attached patch fixes it for me (I used scpexe:// for the target repo, which fails without the patch and succeeds with the patch). The earlier cast to ScpWagon for the lines in question seems overly restrictive and exclusionary.
Rahul Akolkar made changes -
Field Original Value New Value
Attachment MSTAGE-3.patch [ 34630 ]
Benjamin Bentmann made changes -
Link This issue relates to WAGON-209 [ WAGON-209 ]
Hide
Permalink
azgard added a comment -

This address also my error i gotwhen i try to move from http-repo to a dav-repo.

[INFO] ------------------------------------------------------------------------
[INFO] org.apache.maven.wagon.providers.webdav.WebDavWagon cannot be cast to org.apache.maven.wagon.providers.ssh.jsch.S
cpWagon
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.ClassCastException: org.apache.maven.wagon.providers.webdav.WebDavWagon cannot be cast to org.apache.maven.wag
on.providers.ssh.jsch.ScpWagon
at org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:252)
at org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepositoryMojo.java:93)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Show
azgard added a comment - This address also my error i gotwhen i try to move from http-repo to a dav-repo. [INFO] ------------------------------------------------------------------------ [INFO] org.apache.maven.wagon.providers.webdav.WebDavWagon cannot be cast to org.apache.maven.wagon.providers.ssh.jsch.S cpWagon [INFO] ------------------------------------------------------------------------ [INFO] Trace java.lang.ClassCastException: org.apache.maven.wagon.providers.webdav.WebDavWagon cannot be cast to org.apache.maven.wag on.providers.ssh.jsch.ScpWagon at org.apache.maven.plugins.stage.DefaultRepositoryCopier.copy(DefaultRepositoryCopier.java:252) at org.apache.maven.plugins.stage.CopyRepositoryMojo.execute(CopyRepositoryMojo.java:93) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav a:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:227) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Hide
Permalink
Brett Porter added a comment -

applied, thanks. This only genericises to command executors - opened MSTAGE-5 to make it work with others

Show
Brett Porter added a comment - applied, thanks. This only genericises to command executors - opened MSTAGE-5 to make it work with others
Brett Porter made changes -
Assignee Brett Porter [ brettporter ]
Fix Version/s 1.0 [ 13937 ]
Status Open [ 1 ] Closed [ 6 ]
Resolution Fixed [ 1 ]
Benjamin Bentmann made changes -
Link This issue relates to MSTAGE-5 [ MSTAGE-5 ]
Brett Porter made changes -
Link This issue relates to MNG-3581 [ MNG-3581 ]
Brett Porter made changes -
Link This issue is duplicated by MSTAGE-6 [ MSTAGE-6 ]
Hide
Permalink
Dennis Lundberg added a comment -

I'm trying to update the docs for this change, but I'm not sure I understand how wagon works. The patch did not add any new dependencies to the plugin. However, isn't the wagon-ssh-external provider need to use scpexe? Or should that be provided by the project using the plugin?

Regarding what protocols the plugin now supports, am I reading the wagon source correctly if I say the this plugin now supports the following protocols for the target repo?

  • scp:
  • scpexe:

and also this one, which also extends CommandExecutor

  • sftp
Show
Dennis Lundberg added a comment - I'm trying to update the docs for this change, but I'm not sure I understand how wagon works. The patch did not add any new dependencies to the plugin. However, isn't the wagon-ssh-external provider need to use scpexe? Or should that be provided by the project using the plugin? Regarding what protocols the plugin now supports, am I reading the wagon source correctly if I say the this plugin now supports the following protocols for the target repo? scp: scpexe: and also this one, which also extends CommandExecutor sftp
Wendy Smoak made changes -
Link This issue is related to MSTAGE-5 [ MSTAGE-5 ]
Wendy Smoak made changes -
Link This issue is related to MSTAGE-5 [ MSTAGE-5 ]

People

  • Assignee:
    Brett Porter
    Reporter:
    Maria Odea Ching
Vote (1)
Watch (3)

Dates

  • Created:
    Updated:
    Resolved: