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: [email protected]
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
!DSPAM:4517ddd6270429724523251!
---------------------------------------------------------------------
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]
