0 ".Net"s seem to be redundant under /src/contrib/ . It could be something like Analyzers Highlighter Similarity ...
(Maybe, we should find a different name for contrib.net. It contains "contributions specific to Lucene.Net which are not available in Lucene.java) DIGY On Wed, Mar 9, 2011 at 9:08 PM, Prescott Nasser <geobmx...@hotmail.com>wrote: > > Probably just a miss - but under the src/contrib folder you also have a > number of tests in there... > > > Also, is it necessary to have all the sub folders? For the most part the > stuff in contrib.net is contrib.net - why the secondary folder? Unless > that is a requirement of NUnit to have the structure that way it seems a bit > cluttered. > > I would think something like > > src/contrib/contrib.net/ > src/contrib/Snowball.net/ > > instead of > > src/contrib/contrib.net/contrib.net/ > src/contrib/snowball/snowball.net/ > > I don't know how people feel about that > > > ~P > > > ---------------------------------------- > > Date: Wed, 9 Mar 2011 13:31:34 -0500 > > From: mhern...@wickedsoftware.net > > To: lucene-net-dev@lucene.apache.org > > CC: thowar...@gmail.com > > Subject: Re: [Lucene.Net] [VOTE] New Directory Layout for Project > > > > +1 > > > > just a question though. for cmd/bat//sh files for letting people > executing > > the build or just executing other tools from the command line, would > those > > have a place in /bin or somewhere els? This is that someone can just > export > > PATH = / SET PATH= to that one folder and then be able to execute those > > commands from one location? > > > > > > > > On Sun, Mar 6, 2011 at 11:27 PM, Troy Howard wrote: > > > > > All, > > > > > > We'd like to update the project directory structure/layout. > > > > > > See below for a proposed layout. I've also uploaded an example which > > > you can navigate at: > > > > > > > http://people.apache.org/~thoward/Lucene.Net/directory-structure-example > > > > > > NOTE: This will not build!! I just put things in the appropriate > > > places without updating the solution/project files to show how we > > > might lay things out. Also, I included NUnit as an example of a > > > third-party dependency that we might include in the repository under > > > 'lib'. We of course will *not* be distributing NUnit in this manner, > > > due to licensing restrictions. > > > > > > Ok, disclaimer over... > > > > > > Please vote on this layout, or suggest a modification or alternative > > > layout. > > > > > > Voting will be open for 72 hours. > > > > > > [ ] +1 Use this directory structure exactly as described, or with a > > > minor modification > > > [ ] 0 Use a different structure (described in response) > > > [ ] -1 Do not change the directory structure at all > > > > > > > > > Text description of directory schema: > > > > > > Build Files: > > > > > > \build > > > \build\VS2008 > > > \build\VS2010 > > > > > > > > > Source Projects: > > > > > > \src > > > \src\contrib > > > \src\core > > > \src\demo > > > \src\contrib\ > > > \src\core\ > > > \src\demo\ > > > > > > > > > Test Projects: > > > > > > \test > > > \test\contrib > > > \test\core > > > \test\demo > > > \test\contrib\ > > > \test\core\ > > > \test\demo\ > > > > > > > > > Product Documentation: > > > > > > \doc > > > \doc\contrib > > > \doc\core > > > \doc\demo > > > \doc\contrib\ > > > \doc\core\ > > > \doc\demo\ > > > > > > > > > Third-Party Dependencies: > > > > > > \lib > > > \lib\ > > > \lib\\ > > > \lib\\\ > > > > > > > > > Binary Builds: > > > > > > \bin > > > \bin\contrib > > > \bin\core > > > \bin\demo > > > \bin\contrib\ > > > \bin\core\ > > > \bin\demo\ > > >
