On Dec 30, 8:46 pm, Rob Wolfe <r...@smsnet.pl> wrote: > Saul <shaz...@gmail.com> writes: > > Many thanks. This works for me and I find it useful. However, in a > > perfect world: > > > lein compile > > > would also compile my java source code or call compile-java before > > performing a compile.
> If you mean something like Maven "build lifecycle" then I hope > it will be never implemented in Leiningen. I really like tools, > which by default do exactly what I asked for. "lein jar" should only mean > "please create jar on the basis of explicte specification", > nothing more nothing less. I can imagine the maven way of doing things is a pain for plugin developers. However, I have recently moved from the scala maven plugin (which compiles java source automatically) to the clojure maven plugin (which requires an explicit 'mvn compile' to compile java source). I hit two problems where I forgot to compile the java code and thought I was seeing bugs. Its definitely user error (which I can work around) but its worth pointing out that older tools like 'make' would support me in such situations. > If you mean explicit joining of commands, e.g.: > $ lein clean compile-java compile jar > or somehow in project.clj then I'm all in favour of this approach. > I also like this idea but it does make passing parameters to plugins harder. Although I haven't seen any plugins that use parameters yet. Thanks very much for your reply. Saul -- 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
