I'll set up a tripwiresque check of the repository. If anything changes, it will
be reported on (except for things with -SNAPSHOT in their name).
Quoting Brett Porter <[EMAIL PROTECTED]>:
> > I suspect this is the same issue encountered earlier in the month where
> > Dion Gillard had updated/published some jars using maven. At the same
> > point in time some modifications occurred int he directory which we
> > could not identify the origin of.
> Maven was previously setting some funny permissions (recent release
> has fixed that), but I can't think of any reason why it would
> overwrite an existing JAR with a relatively obscure name with
> something different. Not only that, but a selected series of JARs.
> I don't have access to the repo at the moment, but I wonder if it is
> possible that there are still symlinks for those particular snapshots
> and the target was overwritten?
> > The best I personally can do to get this started is to restrict the
> > rights to files that at least I own at the moment (if only because I
> > transfered the content originally from ibiblio to apache) and then
> > transfer the rights to those files to the appropriate group/user on a
> > case by case basis.
> Sounds like a plan.
> > Brett, I'll open these files specifically with write access to the
> > jakarta group, you then should be able to update them. I also recommend
> > that you take ownership of them by moving them to temp files and back to
> > change the ownership to your userid. Then restrict the group ownership
> > so only you (or other Commons Jelly Developers) have rights to write them.
> Will do when I get home.