+1 On Thu, Mar 12, 2009 at 12:17 AM, Alan D. Cabrera <[email protected]>wrote:
> Agreed. When the sample code, especially code that extends/implements > core code, is in a totally different package space the extensions just leap > out at you. This makes things easier to grok. > > > Regards, > Alan > > > On Mar 11, 2009, at 6:46 PM, Erik Beeson wrote: > > As an end user, I think it would be substantially more confusing to have >> the >> example project in the same root package as the core code. If you don't >> like >> example or acme, maybe just "ki." or "ki.examples." or something so it's >> still clear what it's associated with. But to put it in the same root >> package adds confusion for no apparent benefit (it seems to me). >> --Erik >> >> >> On Wed, Mar 11, 2009 at 5:34 PM, Emmanuel Lecharny <[email protected] >> >wrote: >> >> Alan D. Cabrera wrote: >>> >>> >>>> On Mar 11, 2009, at 1:48 PM, Daniel J. Lauk wrote: >>>> >>>> If I may add my two cents... >>>> >>>>> >>>>> I have no issues with that. But why not org.apache.ki.samples.*? I'm >>>>> >>>>>> just >>>>>> curious... >>>>>> >>>>>> >>>>> org.apache.ki.samples sounds good to me. Samples will be found in a >>>>> >>>> separate project anyway, so I don't see how it can be a source of >>> confusion... >>> >>> I think it's better to keep the org.apache prefix. >>> >>> -- >>> -- >>> cordialement, regards, >>> Emmanuel Lécharny >>> www.iktek.com >>> directory.apache.org >>> >>> >>> >>> >
