Just checked and system.log indicates successful authentication.
Tricky to try out sftp, but will do so as soon as my build stops
failing -
artifact downloads are currently being truncated to 64k from my apache
server.
Interesting info about the scp -t option since my client and server are
on the same machine (only have the one), but this hasn't made a
difference before. In fact I've just checked and I can scp files ok by
hand, although I don't use that -t option.
Not been a terribly successful foray into setting up a repository so
far...
(can only get better)
AW
On 7 Oct 2005, at 23:56, Brett Porter wrote:
You're right that it is probably not auth problems, but it's hard for
us to diagnose this for you. I believe others have got scp working on
Mac OS X in general. You probably need to examine the server logs.
the scp -t command is run server side and will copy the file back to
the originating server. You'll find it's what the scp client does on
the client side.
Have you tried sftp:// for deploy? We haven't wired that into site
yet, but it should work unchanged.
- Brett
On 10/8/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
(using mac os x tiger)
I've changed over to using key authent and I still get the same
problem, ie an inexplicable
hang when I deploy to repos. I know my credentials are fine because I
can use them to do the job
manually.
So as an experiment I downloaded the latest maven HEAD just to be
sure I've got
all the latest bugfixes - and bugs - and tried to use site:deploy
which I would
imagine used very similar code. I added the following entry to my
pom:
<distributionManagement>
<site>
<id>agwilliams1000</id>
<url>scp://agwilliams1000.dyndns.org/Users/
ashley/Webroot/</url>
</site>
</distributionManagement>
and when I ran site:site site:deploy I got the following output:
~/projects/xjc-plugin-aw ashley> sudo m2 site:deploy
[INFO] Searching repository for plugin with prefix: 'site'.
[INFO]
---------------------------------------------------------------------
---
----
[INFO] Building xjc
[INFO] task-segment: [site:deploy]
[INFO]
---------------------------------------------------------------------
---
----
[INFO] [site:deploy]
Executing command: mkdir -p /Users/ashley/Webroot/
Executing command: mkdir -p /Users/ashley/Webroot//
Executing command: scp -t /Users/ashley/Webroot//
site49411.zip
and it's still there now as I type trying to do the scp!! Also the
fact that a directory
was created seems to confirm that my credentials are being used
correctly. In
fact I don't think it's hanging, I believe this strange scp -t option
is waiting for
further input - I couldn't even find anything on google that told me
what -t was.
A minor issue is that adding the trailing slash in my url didn't
cause the plugin
to create a subdirectory in Webroot with my artifact name, but
instead from the output
it tried to create Webroot//
Any help at all would be great as I'm sure the site:deploy and m2
deploy problems
are related.
On 7 Oct 2005, at 02:46, Daniel Krisher wrote:
This may not be related, but I remember having problems a while back
because my ssh server was not configured to support plain text
passwords (PasswordAuthentication yes)...
On 10/6/05, andrew <[EMAIL PROTECTED]> wrote:
Hi Ashley,
I have had similar issues to you when attempting to use the scp
protocol
type. See the "[m2] deploy via scp" thread in the list archives.
What I have found is that, as Raphaël has already mentioned, to
use scp
you need to specify all of username, privateKey and passphrase for
each
server in your settings.xml.
If you want to use scp native features (anything in ~/.ssh or via
ssh-agent) you must use the scpexe protocol instead.
See <http://jira.codehaus.org/browse/MNG-712> for some related
info.
Even with the above taken into account there appears to be a bug
generating repository metadata when using scp or scpexe.
See the "[m2] deploy via scpexe -> Unable to retrieve metadata"
thread
and <http://jira.codehaus.org/browse/MNG-925>. This sounds
similar to
what you are experiencing.
Cheers,
...andrew
Ashley Williams wrote:
Hi Raphaël,
It could be that using key authentication makes the difference -
I'll
see if that
works for me. It seems that I have no luck on anything that
involves scp
thus far with Maven.
Thanks
AW
On 6 Oct 2005, at 18:32, Raphaël Piéroni wrote:
Hi Ashley,
I have:
<servers>
<server>
<id>my.snapshots</id>
<username>user</username>
<privateKey>/home/user/.ssh/id_dsa</privateKey>
<passphrase>THE PASS PHRASE</passphrase>
</server>
</server>
in my settings in ~/.m2/settings.xml.
And i have:
<distributionManagement>
<snapshotRepository>
<id>my.snapshots</id>
<name>My Snapshot Central Repository</name>
<url>scp://HOST/WEBDIR/snapshot-repository</url>
</snapshotRepository>
</distributionManagement>
in my pom.xml.
I run: m2 -DupdateReleaseInfo=true install
May that helps.
Best regards,
Raphaël
Ashley Williams a écrit :
I would like to create a separate repository for deploy my
artifacts and as such I've added a section in my pom:
<distributionManagement>
<snapshotRepository>
<id>agwilliams1000-repo</id>
<name>agwilliams1000 Repository</name>
<url>scp://myhost/~/Webroot/maven/
repository</url>
</snapshotRepository>
</distributionManagement>
I've also added a corresponding server tag to my settings.xml.
However, when I run m2 deploy it always hangs
with the message "Retrieving previous build number from
agwilliams1000-repo"
I have no idea what this previous build number might be as I'm
trying to upload the artifact for the first ever time.
Any ideas what the problem might be? I've tried m2 -e deploy
but I
don't get any more information.
Thanks
AW
----------------------------------------------------------------
--
---
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]
--
Daniel Krisher
--------------------------------------------------------------------
-
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]
