Yeah I've got it "mostly" working now with manual metadata removals.
On a side note - it looks like the permissions get written out correctly by
default when I locally modify the snapshotrepo distribution url to use
scpexe:// instead of relying on whatever the default is. (which doesn't
honor gro
only jason can do the chmod or even better run
/www/people.apache.org/repo/m2-snapshot-repository/fix-permissions.sh
if you want to fix it in the meantime, download the metadata files,
delete them in the server and upload again, then run
/www/people.apache.org/repo/m2-snapshot-repository/fix-perm
nevermind, I get it nowam trying a new deploy now
On 4/13/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Thanks Carlos!
Seems that this has happened in more than one place (and is also strangely
the default behavior of my deploy - though when I do it with tapestry on the
same repo it doesn't
Thanks Carlos!
Seems that this has happened in more than one place (and is also strangely
the default behavior of my deploy - though when I do it with tapestry on the
same repo it doesn't even ask for my password as I've done the shared ssh
key thing ) .
Any chance you could chmod -R g+w everyth
i just fixed the permissions, it was owned by jason with no group
perms, but as the directory is group writable you can delete them and
copy again, changing permissions
On 4/13/07, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
While attempting to deploy the new 2.4 snapshot version of surefire I got
While attempting to deploy the new 2.4 snapshot version of surefire I got
somewhat far and then ran into a perm denied for one of the metadata files:
[ERROR] BUILD ERROR
[INFO]
[INFO] Error installing artifact's metadata: Er
