On 09/04/2013, at 10:45 PM, Peter Niederwieser <[email protected]> wrote:
> Luke Daley-2 wrote >> I can't think of much precedence for this kind of thing (attaching >> semantic meaning to package namespacing). > > Attaching semantics to directory names, and indeed also package names, is a > common form of convention over configuration. See Apache Tapestry as an > example: > http://tapestry.apache.org/component-classes.html#ComponentClasses-ComponentPackages So have we "resolved" this issue and are marching forward with the package name approach? -- Luke Daley Principal Engineer, Gradleware http://gradleware.com Join me at the Gradle Summit 2013, June 13th and 14th in Santa Clara, CA: http://www.gradlesummit.com --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
