Aside from what Jason was talking about, the info in my original email
still stands.
All versions of Wagon I tried have the problem of the checksums with
wrong permissions. If you are going to use scpexe to deploy, then you
need to fix that bug. Note you only need to fix, release, and use the
ssh-
Wait, let's regroup for a second. What _exactly_ is the problem with
scpexe again? If it's just a matter of fixing the file modes for the
checksums, can't we simply make a point of fixing this? I understand
that the ssh/scp wagons have some issues related to Jsch, but this
problem (the file mod
Brett Porter wrote:
Jason van Zyl wrote:
Not being able to use scpexe is a problem as the scp deployment is
broken after the introduction of the directory handling code so maybe
that bit should be rolled back in wagon for the time being until it can
be tested properly. If deployment with scpexe
Jason van Zyl wrote:
> Not being able to use scpexe is a problem as the scp deployment is
> broken after the introduction of the directory handling code so maybe
> that bit should be rolled back in wagon for the time being until it can
> be tested properly. If deployment with scpexe is not viable a
Brett Porter wrote:
Hi,
I'm not sure what the story is with Wagon WRT to 2.0.1, as I haven't
seen a recent proposal for a new release. I'm going to assume that the
testing will involve rm -rf'ing any updated plugins from the repo and
using the last release of Wagon.
One thing that needs to be w
Hi,
I'm not sure what the story is with Wagon WRT to 2.0.1, as I haven't
seen a recent proposal for a new release. I'm going to assume that the
testing will involve rm -rf'ing any updated plugins from the repo and
using the last release of Wagon.
One thing that needs to be watched out for - using
