On Fri, Mar 27, 2009 at 2:38 AM, Greg Brown <[email protected]> wrote: >>> We already have an Ant build, which is actually why I'm asking the >>> question. Our SVN repository is laid out in such a way that our Ant script >>> can easily build from it. In other words, it is optimized for Pivot >>> *developers*. Our source artifact is laid out such that it is easily >>> browsable by Pivot *users*, who may be interested in looking at the source, >>> but not necessarily building it (for example, I have often looked at the >>> source code for the JDK, but I have never attempted to build it). We see >>> these as two very distinct use cases, so we have structured our release >>> artifacts accordingly. >> >>This is not a problem. Just note that The ASF releases Source. We're >>Open Source after al :) > > Of course. :-) > > Glad to hear that our current approach is OK, because I do think that > source-code savvy users (not developers) will find it easier to navigate. >
I am not sure what you are agreeing on here. The Source Release Tarball MUST be buildable through provided instructions. Now, you can simplify the instructions and say "cd apache-pivot ; ant install" or go through all the steps required to produce a document that any "regular Java developer" (or preferably "any developer") without prior knowledge of your chosen toolset. I am sure that the latter will be a lot more long-term pain, than the former. Checking out from SVN is not an acceptable solution. It is lacking all security features and it is possible for people to manipulate the tagged sources without anyone noticing... Cheers Niclas -- http://www.qi4j.org - New Energy for Java
