Hi, I noticed some namespace inconsistencies that we might want to clean up before our first Apache release. Now would be the best time to do this while the number of affected users is still relatively small.
Module "crunch": Right now "Crunch" means both the Java framework and the parent project that includes Scrunch and the other modules. We talked about crunch-core informally, so maybe we should rename the module and the artifactId to make it consistent with crunch-examples, crunch-test, and many other projects that use this naming scheme. If there are plans to modularize crunch some more (ie. move sub-frameworks like aggregation or joins to their own modules) we could also change the Java package namespace to "org.apache.crunch.core". Module "scrunch": Maven coordinates are currently "org.apache.crunch:scrunch" but the Scala packages are in "org.apache.scrunch"; I don't know if we're allowed to use this namespace. If not, I'd suggest to use "org.apache.crunch.scrunch" and maybe even change the Maven module to "crunch-scala" (because "crunch-scrunch" sounds really, really weird). Module "examples": I'd change the module name to "crunch-examples" to match the artifactId. While module renaming doesn't affect users, changing artifactIds forces them to change their POMs, and package renaming leads to either scripting efforts or mass "Organize Imports". What do you think? Regards, Matthias, who knows he keeps bringing up unpopular topics
