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 Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Package-names-for-tasks-and-plugins-tp5711007p5711132.html Sent from the gradle-dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
