: another ant target that creates an example dir outside of the tree?
The example is just an example - most of our users will never run "ant
example" anyway (it's done before the release is packaged up)
making "ant example" copy the example configs to ./build/example and the
only packaging tht
Suggestion,
another ant target that creates an example dir outside of the tree?
I was a little bit surprised by the following scenario:
1) svn co
2) ant example
3) edit schema.xml
4) svn st
In the future, I'll run cp -r before I start messing with the example.
I'm +1 for the work directory.
I
Jetty unpacks the war in a sub-dir of /tmp by default (which can get
cleaned by other things).
https://issues.apache.org/jira/browse/SOLR-118
devs: any reason we shouldn't create example/work and make sure it
gets in the distributions?
-Yonik
On Fri, Mar 7, 2008 at 7:19 AM, Doug Steigerwald
<[E
