that's very ssh specific, more complex scenarios would use archiva and
control there the permissions.
if you want the ssh wagon look for the properties and use them if
present cool, but it'd be easier now to apply and test the patches in
WAGON-19
On 4/13/07, Jason van Zyl <[EMAIL PROTECTED]> wro
On 13 Apr 07, at 12:28 PM 13 Apr 07, John Casey wrote:
so, would the deploy plugin read these properties and set them on
the wagon
at deployment time,
Yah, the deployer in maven-artifact would use this and pop the right
things into Wagon.
or would you have some sort of cron job to keep
On 13 Apr 07, at 12:27 PM 13 Apr 07, Carlos Sanchez wrote:
WAGON-19 and MDEPLOY-28 have patches that would solve the problem with
metadata permissions among others.
We could also just make the properties a little more sophisticated to
allow for variation. I think just having a reference be
so, would the deploy plugin read these properties and set them on the wagon
at deployment time, or would you have some sort of cron job to keep things
honest? I'm guess you'll have to have both, since older versions of the
deploy plugin won't know to look for the repo.properties...
Overall, I thi
WAGON-19 and MDEPLOY-28 have patches that would solve the problem with
metadata permissions among others.
On 4/13/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
Hi,
I'm tired of screwing around with deployments not working with the
right permissions and groups. The last fix to the deployments ma
Hi,
I'm tired of screwing around with deployments not working with the
right permissions and groups. The last fix to the deployments make
the permissions decent by default but that's not enough as I deployed
something that didn't have a group at all.
So I would like to propose using a sim
