Hi, On Jul 8, 7:25 am, j-g-faustus <johannes.fries...@gmail.com> wrote:
> So maybe it's best to use the Java convention after all? > It has been proven to scale, is widely used and plays well with > whatever else is running on the JVM, which are strong points in its > favor. I still don't buy it. The company I work for changed its domain over 4 years from contiteves.com over contiautomative.com to continental- corporation.com and maybe its soon schaeffler-continental-automotive- group.com or whatever. Should I always touch each and every code module to fix the package names? Just to understand the problem (honest questions; I don't know the answers): How many open source projects are out there, which have the same names? Is a clash in project names, that likely? What happens with the prefix-with-your-domain prefix can be seen on clojars at the moment. People upload stuff under names they don't own. There are several vimclojure packages. Not a single of these are projects on their own right. Just variants of mine. Maybe patched, maybe not. Nothing is documented. How does that help anything? How should the casual user know which is the official one? Maybe following the Java convention is good. Maybe not. What is the convention on the CLR? What happens if both conventions contradict? We should choose a convention based on arguments and not based on what others do. Sincerely Meikel -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
