I remember reading somewhere[1], that we can actually run ant from maven. It just occurred to me, that we can build the pom with groupId, artifactId and version, which actually uses ant for the build. This way the builds will be identical and we'll only have to update the version in the pom.
I don't have the time right now, but I can try to build the pom in the weekend. [1] Probably here: http://books.sonatype.com/maven-book/index.html On Dec 4, 8:59 pm, Luke Amdor <[EMAIL PROTECTED]> wrote: > As an avid Maven fan, I really don't think Clojure would really > benefit much from having a Maven build. It really doesn't have any > dependencies to speak of and is extremely easy to build. > > The main thing that I would like to be able to do is to easily get the > newest Clojure snapshots and releases. So being able to refer to a > dependency on Clojure in my own project's pom.xml is important to me. > > Just my 2c. > > Luke > > On Dec 4, 7:24 am, verec <[EMAIL PROTECTED]> > wrote: > > > +1 (avoid Maven, drop pom) > > > I'm just out of a project that has used Maven for more than 18 month. > > The pain and frustration caused by the slowness and compexity of > > Maven's "download the whole internet" approach can be matched only > > bu the willingness of team astronauts to introduce Maven plugins in > > the build process, more often that not to fix an endogenous problem. > > > +1 (keep Ant) > > -- > > JFB --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
