[jira] Commented: (MPARTIFACT-61) scpexe is a noop

["Joerg Schaible (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MPARTIFACT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92984 ] 

Joerg Schaible commented on MPARTIFACT-61:
------------------------------------------

Not a problem anymore, at least for me ... using M2 since 1 year ;-)

> scpexe is a noop
> ----------------
>
>                 Key: MPARTIFACT-61
>                 URL: http://jira.codehaus.org/browse/MPARTIFACT-61
>             Project: maven-artifact-plugin
>          Issue Type: Bug
>    Affects Versions: 1.5.2
>         Environment: Windows / Cygwin / Maven 1.0.2 / JDK 1.4.2
>            Reporter: Joerg Schaible
>            Assignee: Arnaud Heritier
>            Priority: Blocker
>
> Unfortunatel scpexe protocoll seems a noop in version 1.5.2. The executable is not called, but Maven is reporting happily that it has deployed:
> jar:deploy:
>     [echo] Deploying...
> Using userBuildPropertiesFile: C:\Dokumente und Einstellungen\jos\build.properties
> Using projectPropertiesFile: C:\Work\Projects\commons\lang\project.properties
> Using projectBuildPropertiesFile: C:\Work\Projects\commons\lang\build.properties
> Will deploy to 1 repository(ies): elsag
> Deploying to repository: elsag
> Uploading to elsag-commons/poms/elsag-lang-1.2-SNAPSHOT.pom: 
> .................... (7K)
> Uploading to elsag-commons/poms/elsag-lang-snapshot-version: 
> .................... (0K)
> Uploading to elsag-commons/poms/elsag-lang-1.2-20051011.091919.pom: 
> .................... (7K)
> Will deploy to 1 repository(ies): elsag
> Deploying to repository: elsag
> Uploading to elsag-commons/jars/elsag-lang-1.2-SNAPSHOT.jar: 
> .................... (64K)
> Uploading to elsag-commons/jars/elsag-lang-snapshot-version: 
> .................... (0K)
> Uploading to elsag-commons/jars/elsag-lang-1.2-20051011.091940.jar: 
> .................... (64K)
> attaining goal build:end
> I can even remove any scp.exe and ssh.exe or set maven.repo.X.scp.executable to any not existing file, the output of Maven is the same. Setting the scp.executable property to a batch file that writes something into a file proves, that the "executable" is definately not called. All this works with 1.4.1 though delivered with the M102 installation, the artifacts are really delpoyed.
> This is a real blocker for me, since I am stuck to 1.0.2 because of extensive entitiy usage and I wanted to use 1.5.2 to write self-contained POMs into the repository to prepare a M2 transition at a later time.
> Note, that the scp protocol does not work either for me, I always get despite any settings for private key and passphrase:
> Root cause
> org.apache.maven.MavenException: Unable to deploy to any repositories
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy(DefaultArtifactDeployer.java:338)
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleDeploy(DefaultArtifactDeployer.java:131)
>         at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:102)
>         at org.apache.maven.artifact.deployer.DeployBean.deploy(DeployBean.java:142)
>         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:324)
>         at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230)
>         at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145)
>         at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
>         at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:125)
>         at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
>         at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
>         at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
>         at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
>         at com.werken.werkz.Goal.fire(Goal.java:639)
>         at com.werken.werkz.Goal.attain(Goal.java:575)
>         at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
>         at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
>         at org.apache.maven.cli.App.doMain(App.java:488)
>         at org.apache.maven.cli.App.main(App.java:1239)
>         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:324)
>         at com.werken.forehead.Forehead.run(Forehead.java:551)
>         at com.werken.forehead.Forehead.main(Forehead.java:581)

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira