+1 (avoid Maven, keep POM) I'm moving Tapestry away from Maven as soon as I get chance, but I'll still have a POM for each module, and I'll still distribute it to the Maven central repository ... that part is the one thing that Maven gets really right.
In some ways, avoiding Maven for the build is better, since it'll be easier to do a couple of things. I feel strongly that the Java API should be generated as Javadocs, and linked to from the real clojure home page, as should test reports when tests are ready. On Wed, Dec 3, 2008 at 6:55 AM, Christian Vest Hansen <[EMAIL PROTECTED]> wrote: > > On Wed, Dec 3, 2008 at 3:01 PM, ivant <[EMAIL PROTECTED]> wrote: >> I'm a Maven fan, and I think it'll be good if clojure supports it. >> But "support" here can mean different things. And the minimal >> "support" for maven could be to just drop the clojure.jar in public >> maven repository. > > And a pom with groupId, artifactId and version, so the jar can be > refered from other poms. > > -- > Venlig hilsen / Kind regards, > Christian Vest Hansen. > > > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --~--~---------~--~----~------------~-------~--~----~ 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 To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
