Martin Burger schrieb am 02.09.2005 14:05:
I want to deploy a jar to my remote repository. But the goal
jar:deploy hangs. On the linux machine (Debian Sarge) there are some
zombie / defunct processes. If I kill such a process, the goal
continues until the next process hangs. The processes are
Martin Burger wrote on Friday, September 02, 2005 2:06 PM:
Hello!
I want to deploy a jar to my remote repository. But the goal
jar:deploy hangs. On the linux machine (Debian Sarge) there are some
zombie / defunct processes. If I kill such a process, the goal
continues until
the next
Well, IMHO, maven.repo.foorepo.ssh.executable and
maven.repo.foorepo.scp.executable seem like they have to be Windows
executables, since the jar has to be deployed from Windows to Linux...
--- Jörg Schaible [EMAIL PROTECTED] a écrit :
Martin Burger wrote on Friday, September 02, 2005 2:06 PM:
Yann Le Du wrote on Friday, September 02, 2005 2:48 PM:
Well, IMHO, maven.repo.foorepo.ssh.executable and
maven.repo.foorepo.scp.executable seem like they have to be
Windows executables, since the jar has to be deployed from Windows to
Linux...
OK, this is different. In that case I assume,
Jörg Schaible schrieb am 02.09.2005 14:42:
Well, yes. You execute Maven on Linux and expect it to respect DOS/Windows
paths and executables. So what do you expect?
Because I deploy from a German Windows XP machine to a Debian box I
expect that it works. ;-)
Regards,
Martin
Jrg Schaible schrieb am 02.09.2005 14:51:
Well, IMHO, maven.repo.foorepo.ssh.executable and
maven.repo.foorepo.scp.executable seem like they have to be
Windows executables, since the jar has to be deployed from Windows to
Linux...
OK, this is different. In that case I
Martin Burger schrieb am 02.09.2005 14:53:
Because I deploy from a German Windows XP machine to a Debian box I
expect that it works. ;-)
Uups, that does not mean that a German XP is better as another one. But
perhaps the different languages on the systems cause the problem...
Martin Burger wrote on Friday, September 02, 2005 2:56 PM:
Jörg Schaible schrieb am 02.09.2005 14:51:
Well, IMHO, maven.repo.foorepo.ssh.executable and
maven.repo.foorepo.scp.executable seem like they have to be
Windows executables, since the jar has to be deployed from Windows to
Linux...
Jörg Schaible schrieb am 02.09.2005 15:06:
What happens if you start plink manually (with the options from the Maven
proeprties file)?
Get the executed command from Maven by calling it with -X option.
Using -X option shows a lot of [DEBUG] messages, but no commands:
[DEBUG] Could not load
Jörg Schaible schrieb am 02.09.2005 15:06:
What happens if you start plink manually (with the options from the Maven
proeprties file)
C:\\Programme\\INet\\Remote\\PuTTY\\plink.exe -A -2 -ssh
[EMAIL PROTECTED]
Using username auser.
Linux ahost 2.6.11.9-050512a #1 SMP Thu May 12 20:53:02
Martin Burger wrote on Friday, September 02, 2005 3:35 PM:
Jörg Schaible schrieb am 02.09.2005 15:06:
What happens if you start plink manually (with the options from the
Maven proeprties file)
C:\\Programme\\INet\\Remote\\PuTTY\\plink.exe -A -2 -ssh
[EMAIL PROTECTED] Using username
Jörg Schaible schrieb am 02.09.2005 16:00:
Just start a remote command:
plink -A -2 -ssh [EMAIL PROTECTED] ls -l
This should give you a list of your home directory on the remote server. You
should not have to press any key or logout manually.
Strange.
plink.exe -A -2 -ssh [EMAIL
Martin Burger wrote on Friday, September 02, 2005 4:45 PM:
Jörg Schaible schrieb am 02.09.2005 16:00:
Just start a remote command:
plink -A -2 -ssh [EMAIL PROTECTED] ls -l
This should give you a list of your home directory on the remote
server. You should not have to press any key or
13 matches
Mail list logo
