> Hmm.. I'd leave ant, which is rather hybrid in nature, but I've always > thought of Maven as being strongly functional. Of course it's not > completely functional, as there's the life cycle, but artifacts are a > function of another artifact or a set of other resources. > I don't see a contradiction in the fact that it's declarative, as this > just means that there's a standard set of functions that you just > parametrize.
Indeed there isn't any contradiction between being declarative and functional. Often the fact that you can achieve a given task in a declarative way means that it has been implemented or at least thought in functional programming style under the hood. Just to bring another example based on my personal experience, with lambdaj I tried to provide a way to manipulate java collections in a declarative way exactly because I had FP in mind. Mario Fusco twitter: @mariofusco -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
