Hello Our svn repos are configured with only trunk/tags/branches at the top level. If I remember correctly this is recommended by maven.
I suppose in theory there is no reason not to have other top level folders as long as maven ignores them. Is anyone doing this? Our developers need access to any active branches and the trunk. They are also allowed to create their own tags as long as they dont collide with release tags. We now have documenters/testers/mgrs that are not experienced with svn so I was asked to investigate limiting their access. Unless there is a nice ui to manage this it seems to me like it could quickly turn into an administrative blackhole. I really appreciate your mentioning that client bug btw, that would have caught me (given our version) Regards, Gord [email protected] On Fri, Jan 7, 2011 at 5:01 PM, Dennis Lundberg <[email protected]> wrote: > On 2011-01-07 17:14, Gordon Cody wrote: > > Hello List > > > > Svn repositories allow for access permissions to be set at the directory > > level. > > > > Maven seems to expect that developers have access to the entire > repository. > > What makes you think so? > > I use Maven against an SVN repo where I do not have read access to the > entire repo. There were some problems at first, but those were due to a > bug in the Subversion client. After I upgraded to Subversion 1.6.12 (I > think, I'm not on that machine right now), things have worked smoothly. > > > Is there a way to reconcile these differences such that some people (for > > example > > junior, qa or non technical people have access only to certain portions > of > > the repo? > > > > Regards, Gord > > [email protected] > > > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
