: > I'm not ant expert, but I'm a little uneasy about the way "ant example" : > copies build artifacts from dist into what is really a source directory : > (./example). : : I had considered example to be a binary directory, like lib (and hence : not under source).
yeah, i ment "source" as in directory that is commited into CVS, as opposed to "a directory where stuff compiled from source get's copied" ... copying the war into ./example seems analogous to copying the solr.jar into ./lib .... it's just dirty. : > * "ant example" should copy everything from : > ./example to ./build/example : : in which case maybe example should go under src... +1 : > * "ant package" rely only on the files it can find in the dist : : Why is that? It's just what seemed to make sense given the stages of our build.xml ... compile/example/javadoc/test take files under version control and process them into usable entities - complaining about any errors they may find; dist* takes artifacts from the previously stage and bundles each set into into individual zip files; package takes artifacts from the previous stage and bundles them into a single zip file. : I took the shortest path I knew in getting a nightly binary : distribtion (and I modeled the layout based on nightly builds from : nutch/hadoop/lucene). So if things can be cleaned up, go for it... : i'm more interested in the results (the actual layout of the final : .zip) I'm leary of cleaning it up myself ... mainly because all of these ideas are just what make sense to me, and i'm one of hte least knowledgable ant people i know (both in terms of what is possible and in terms of what is convetion) ... if what we've got right now more closely mirrors our sister projects then i say we stick with it, but one thing we should definitely try to fix is that... svn checkout ...; cd ...; ant package clean; svn status ...shouldn't warn about finding files not under version control. That may mean making "clean" smarter about all the various places build artifacts wind up, or it may mean moving those artifacts to directories it already knows about. I vote for the latter. -Hoss
