On 5/4/07, James Strachan wrote: > We've already got quite a few modules in subversion & we are starting > to use lots of snippets on the wiki. I figured now was agood time to > ponder about the directory layout (the sooner we finalise on a layout > the better as it avoids hours wasted updating the wiki). > > We could do things like servicemix & CXF where we have some top level > directories to group maven projects together. > > I'm wondering about something like this... > > camel-core/ > // the core root module > > components/ > camel-jms > camel-mail > camel-spring > ... > > examples/ > camel-example-jms-file/ > ... > > tooling/ > camel-eclipse/ > maven-plugins/ > .. > > apache-camel/ > // the assembly > > itests/ > // integration testing stuff? > > Am liking the idea of leaving camel-core in the root; firstly as the > huge amounts of javadoc & snippet macro links wouldn't have to change > - but also its pretty much the core folks should start with before > moving onto other modules. > > Thoughts? +1 I really like the way that ServiceMix is organized. It's easy to see at a glance where the core is vs. each component. Not only is it logical but it's also nice when browsing and searching the dir structure. Bruce -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E