Hi,
        Some thoughts that I want to share on this thread. Here are the
points  we think mainly differentiate maven2 and Ivy.

        1. Maven2 is a software project management and comprehension
tool,   whereas Ivy is only a dependency management tool, highly
integrated      with Ant, the popular build management tool.
        
        2. Ivy heavily relies on a unique concept called configuration.
In      ivy, a module configuration is a way to use or to see the
module. For     instance, you can have a test and runtime configuration
in your         module. But you can also have a mysql and an oracle
configuration. Or       a hibernate and a jdbc configuration. In each
configuration you can   declare what artifacts (jar, war, ...) are
required. Maven2 on its         side has something called the scope. You
can declare a dependency as     being part of the test scope, or the
buildtime scope. Scopes are     predefined in maven2 and you can't
change that.

        3. Ivy let you do whatever you want: use one conflict manager in
one     module, another one elsewhere, decide which revision you will
get,    you can even plug your own conflict manager if you need to. With
maven2, conflict management is quite simple: the principle is to get
the nearest definition.
        
        4.  In Ivy many things can be configured, and many others can be
plugged in: dependency resolvers, conflict manager, module descriptor
parser, latest revision strategy, ...
        Maven2 also offers repository pluggability, but not much more as
far     as we know. Moreover, repository configuration is much less
flexible        than with Ivy: no repository chaining, no way to split
metadata and    artifacts in multiple repositories.     


Regards,

 

Mayank Upadhayay* Software Engineer* SunGard * Technology Services *
Divyasree Chambers Langford Road Bangalore 560025 India 
Tel +91-80-2222-0501 * Mobile +91-9986731792 * Fax +91-80-2222-0511 *
www.sungard.com

P Think before you print

CONFIDENTIALITY: This email (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this email in error,
please notify the sender and delete this email from your system. Thank
you.


-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dion
Dodgen
Sent: Tuesday, January 29, 2008 10:25 PM
To: Developer
Subject: Re: [Mifos-developer] dependency management

Hi Steve,

I'm all for dependency management.

I have only used Maven, do you know of any similarities with Ivy apart
from the obvious dependency management :) ie. repositories etc. guess
I should take a look.

Dion - (J2EE in JBoss :))

On Jan 29, 2008 8:44 AM, Stephen Horgan <[EMAIL PROTECTED]> wrote:
> Hi all,
> firstly, I forgot to introduce myself yesterday before I sent the
patch for
> bug 1533 (I did said hello on IRC but not here)...
> So, I'm a J2EE developer in IBM with experience in SpringMVC,
JavaServer
> Faces, Hibernate, iBatis & JDBC, and I joined the mifos project just
last
> week.
>  I'm keen to help in any way, so let me know how I can do :-)
>
> I'm wondering what people think about the idea of introducing a simple
> dependency management solution. I've experience with Apache Ivy which
> integrates very nicely with Ant, and in my opinion would require
minimal
> effort to integrate into the existing Mifos setup.
>  There are lots of jars in Mifos, and some of those are unversioned
and
> perhaps even unused. I know this probably isn't a problem as such at
the
> moment but for future development, and to allow for possible
modularity and
> reuse, a dependency manager such as Ivy could be of use. What do
people
> think?
>
> I can attempt to create an Ivy config for mifos over the next few days
> unless anyone has objections?
>
> Regards,
> Steve
>
>
------------------------------------------------------------------------
-
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Reply via email to