> On 10/22/2010 19:15, Marshall Schor wrote: >>> On 10/22/2010 18:06, Marshall Schor wrote: >>>>> On 10/22/2010 17:02, Marshall Schor wrote: > [...] >>>> Note also that you don't need to fiddle before building - this is more >>>> like a >>>> one-time setup that tells your maven installation that it can reference the >>>> Apache Maven Snapshot repository for artifacts - and that is where >>>> unreleased >>>> things are. >>> It really makes no difference. I expect to be able >>> to extract the source code from svn onto a clean >>> machine and build it without any extra setup. Every >>> other open source project that I know works that >>> way, and I see no good reason why we should be >>> different. >> >> We could do this, but it would impose the requirement that the build tooling >> be >> in a particular, fixed relative location relative to the other projects. I >> was >> trying to decouple these. > > How so? When I built last night, I did a "mvn install" > on the build tools. My hazy understanding of the process > tells me that puts them in my local repo somehow, and > that makes the location of the source irrelevant, doesn't > it?
Yes, exactly right. My comment was for the case where the user *didn't* first checkout and "mvn install" the build tooling first. > > I'm fine with having to explicitly build the build tools > first, if that's what you mean. OK. I've added that "style" to the one-time setup on our web site as the 1st of 2 alternatives. -Marshall > > --Thilo > >
