On 4/16/02 5:18 PM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Henri Yandell <[EMAIL PROTECTED]> wrote on 17/04/2002 12:08:06 AM: > >> >> I think we're working towards having a real problem towards the consumer >> as to the difference between Maven and Jjar and why there are two tools >> with such an overlap. >> >> I'd recently flipped my 'consumer' demands over to Maven. Do you see any >> forseeable solutions? > Choice. > > At the moment Maven is a lot wider scope than JJar, and a lot more mature. > That's like saying Tomcat is a lot wider scope than Ant and a lot more mature. :) My point is that we are comparing apples to oranges - they aren't intended to solve the same problem. Yes, Maven needs to know about dependencies and have jars to satisfy the dependencies, but so does a classloader... Here's a limited list of what maven does, and given the development frenzy surrounding it, I can say this is accurate only as of 17:18EST 20020416 : * Change log document created directly from repository information. * Cross referenced sources * Source metrics * Mailing lists * Developer list * Dependency list * Unit test reports including coverage * Article Collection * Software Development References * Software Development Process Documentation * Distribution publication based on the POM. JJAR gets jars and dependency jars. That's it. -- Geir Magnusson Jr. [EMAIL PROTECTED] System and Software Consulting The cost of synchronization is much less that the cost of stupidity. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
