On 10/26/2010 17:27, Thilo Götz wrote: > On 10/26/2010 17:14, Marshall Schor wrote: >> >> >> On 10/26/2010 8:02 AM, Jukka Zitting wrote: >>> Hi, >>> >>> On Tue, Oct 26, 2010 at 2:10 PM, Marshall Schor <[email protected]> wrote: >>>> So, well, this isn't quite correct. Things placed here get copied into >>>> the top >>>> of the top project, not the top level of the archive. >>> Couldn't the top project simply be at the top level? Then this >>> wouldn't be a problem. Convention over configuration, as they say. >>> >> >> Good point. >> >> We're currently using a "flat hierarchy" organization for our multi-module >> project, due to our Eclipse IDE legacy. >> >> Archive >> top-dir-of-archive >> top-project >> README >> LICENSE >> NOTICE >> RELEASE_NOTES etc. >> other project1 >> other project2 >> >> I was trying for: >> >> Archive >> top-dir-of-archive >> top-project >> other project1 >> other project2 >> README >> LICENSE >> NOTICE >> RELEASE_NOTES etc. >> >> I agree that we could restructure to eliminate the top-dir-of-archive, and >> restructure things to have the top-project be that directory. That might >> break >> some Eclipse things related to multi-module projects, so would need to be >> tried >> out and tested. > > Would it be a problem if the README etc. don't show up > in Eclipse? You don't need more than a text editor for > those, and you can check in a couple of files from the > command line. (Or maybe I'm misunderstood)
Strike the 'm > > --Thilo > >> >> -Marshall >> >>> Jukka Zitting >>> >>>
