Adam Murdoch wrote > We could possibly implement this by traversing and inspecting the static > dependency graph between types, so that, for example, a type that is > reachable from a Task type cannot then depend on any Task or Plugin types. > > I think, however, naming scheme is the simplest option - this might mean > prefixing or suffixing types with their role, or separating roles into > packages, or some combination.
If we truly need to know the roles at compile time, and not just for plugin and task classes, then a package naming scheme is the clear winner for me. Question is how to make things work for all the existing code that doesn't fit the agreed upon naming scheme. Cheers, Peter -- View this message in context: http://gradle.1045684.n5.nabble.com/Package-names-for-tasks-and-plugins-tp5711007p5711096.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
