DM, I create one project (new project, checkout projects from SVN, and let it set it as a java project). I then set the source folders like you mentioned below. I add lib/junit*whatever.jar to library classpath, and set UTF-8 default encoding for the project. and set the formatter to the lucene style xml file here: http://wiki.apache.org/lucene-java/HowToContribute
for the ones you have mentioned, you shouldnt have dependencies between contribs, you dont need any more source folders. Here is my pattern, I want to have projects for > lucene-core > lucene-core-tests > lucene-core-demos > lucene-analyzers-common > lucene-analyzers-common-test > lucene-analyzers-smartcn > lucene-analyzers-smartcn-test > ... > That is one for each separate jar and one that separates test from code. > And I want to use an external checkout of all of lucene. So I can update > from the root, run ant, create fully pathed patches, .... > > Doing this is a real pain, taking over 4 hours, including some "don't do > that" learning. > > The dependencies between contribs is not documented well, so that took some > time to figure out. > > Maybe, I'm just stuck on a favorite pattern that I've used for years and > there's a better way... I'd like to know how it can take "10 seconds or so". > > > -- DM > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-dev-h...@lucene.apache.org > > -- Robert Muir rcm...@gmail.com
