If you get authentication failure, it's normal to have the password prompt.
You can perhaps try with the latest wagon jars (1.0-beta-1)
Emmanuel
Ravinder Singh a écrit :
Maven is 2.0.4, deploy is 2.2.1 and wagon-provider-api:jar:1.0-alpha-5
Tried using -B also, but says:
[INFO] Error deploying artifact: Authentication failed: Cannot connect. Reason:
Auth fail
-----Opprinnelig melding-----
Fra: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sendt: 26. september 2006 10:44
Til: Maven Users List
Emne: Re: SV: SV: SV: SV: deploy with scp
What is your maven, wagon provider and deploy plugin versions?
Emmanuel
Ravinder Singh a écrit :
Output with mvn -X (only the endpart):
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from inhouse_snapshot [DEBUG]
adding permissions to wagon connection: 664 775
Password: :
It seems that it sets the permissions correctly from the settings.xml (if I
change the permissions it is reflected in the debug log), but it does not seems
the read the password tag.
-----Opprinnelig melding-----
Fra: Ravinder Singh [mailto:[EMAIL PROTECTED]
Sendt: 26. september 2006 10:14
Til: Maven Users List
Emne: SV: SV: SV: SV: deploy with scp
I tried using help:effective-pom and effective-settings, and it shows the
correct pom and the correct settings.xml. However it still asks for password. I
tried to copy the settings.xml to mavens bin directory (which is in %path%),
but same result.
-----Opprinnelig melding-----
Fra: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sendt: 26. september 2006 09:25
Til: Maven Users List
Emne: Re: SV: SV: SV: deploy with scp
Ravinder Singh a écrit :
It is currently under ${user.home}/.m2/settings.xml
Is it the user.home directory of the user that run Continuum?
By running manually: mvn deploy fails too, and asks for password.
You can run 'mvn help:effective-pom' and 'mvn help:effective-settings' so
you'll can verify that maven used correct files.
Emmanuel
-----Opprinnelig melding-----
Fra: Naess, Ronny [mailto:[EMAIL PROTECTED]
Sendt: 26. september 2006 09:01
Til: Maven Users List
Emne: SV: SV: SV: deploy with scp
Emmanuel, what we did was to check in maven as a tool into SVN
together with the project. Each user has to configure M2_HOME, and
the advantage with this setup is a common settings.xml for every user.
Very Team Colloboration friendly :-)
-Ronny
-----Opprinnelig melding-----
Fra: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sendt: 26. september 2006 08:59
Til: Maven Users List
Emne: Re: SV: SV: deploy with scp
My question was where is it?
is it under ${user.home}/.m2 or ${m2.home}/conf/settings.xml?
Continuum doesn't read ${m2.home}/conf/settings.xml.
Emmanuel
Ravinder Singh a écrit :
I allready had it in the previous message, but posting it again for those who
failed to see it....
My settings.xml:
-----------------------------------------------------------
<server>
<id>inhouse</id>
<username>maven</username>
<password>maven</password>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
<server>
<id>inhouse_snapshot</id>
<username>maven</username>
<password>maven</password>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
-----------------------------------------------------------
-----Opprinnelig melding-----
Fra: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sendt: 25. september 2006 17:25
Til: Maven Users List
Emne: Re: SV: deploy with scp
Where is your settings.xml?
Emmanuel
Ravinder Singh a écrit :
I have done exactly the same! But I am testing under windows and
deploying to linux through ssh.
It keeps asking me for the password....I am not using external ssh.
My POM:
...
<distributionManagement>
<repository>
<id>inhouse</id>
<name>inhouse</name>
<url>scp://xxx.xxx.xxx.xxx/home/maven/repos/inhouse</url>
</repository>
<snapshotRepository>
<id>inhouse_snapshot</id>
<name>inhouse snapshot</name>
<url>scp://xxx.xxx.xxx.xxx/home/maven/repos/inhouse_snapshot</url>
</snapshotRepository>
</distributionManagement>
My settings.xml:
<server>
<id>inhouse</id>
<username>maven</username>
<password>maven</password>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
<server>
<id>inhouse_snapshot</id>
<username>maven</username>
<password>maven</password>
<filePermissions>664</filePermissions>
<directoryPermissions>775</directoryPermissions>
</server>
-----Opprinnelig melding-----
Fra: Naess, Ronny [mailto:[EMAIL PROTECTED]
Sendt: 25. september 2006 16:47
Til: Maven Users List
Emne: SV: deploy with scp
Hi, Ravinder my friend.
This is how I do it. Note I use user/password.
Settings.xml
---------------------------
<server>
<id>website</id>
<username>apache</username>
<password>apache</password>
<filePermissions>644</filePermissions>
<directoryPermissions>755</directoryPermissions>
</server>
---------------------------
Pom.xml
---------------------------
<distributionManagement>
<site>
<id>website</id>
<url>scp://sgm636/opt/web/ansattportal</url>
</site>
</distributionManagement>
---------------------------
-Ronny
-----Opprinnelig melding-----
Fra: Ravinder Singh [mailto:[EMAIL PROTECTED]
Sendt: 25. september 2006 15:46
Til: users@maven.apache.org
Emne: deploy with scp
I am trying to do do a deploy without user interaction (through
continuum).
Currently I am testing deploy for the project. But I am failing to
have it deploy without prompting for password.
I hace specified the privateKey, username, and even the password in
the settings.xml. But it won't stop asking for password.
However a release:perform does not ask for a password and does
everything automagically, without prompting for password, so here
it works with scp and privateKey.
Is there any workaround for this or am i doing something wrong?
Ravinder Singh
System developer
-------------------------------------------------------------------
-
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------
-
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!DSPAM:4518cfb450682065019448!
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
