--- Jose Gonzalez Gomez <[EMAIL PROTECTED]>
wrote:
> 
>     I still don't see the diference or relation
> between maven.xml and 
> build.xml. From what I read and your answers I
> understand that maven is 
> thought for the development of a "monolithic"
> application or library, 
> the one that tipically is bundled in one jar, am I
> right?

Yep. Maven is really powerfull for such task. 
Of course you can produce several artifacts from
single project, but easier way would be to structure
your code
and use reactor to pull the things together. 

Maven is really nice when it comes to active
development of several dependent  projects at the
same time. Right now, we have 4 projects and 4
developers, without clear separation. 

Dependency management ( and artifact distribution )
would be plain unmanageable without maven... )


>     So if you need a custom build, you still may use
> ant... but can you 
> call this build from maven, or must you call ant
> directly?

You can call any ant task from maven.xml - 
because maven uses ant behind the scenes ( but not
only ant )

Think of goals defined in plugins as pre-cooked 
ant tasks. 

regards,

=====
Konstantin Priblouda ( ko5tik )    Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >

__________________________________________________
Do you Yahoo!?
Yahoo! Tax Center - File online, calculators, forms, and more
http://tax.yahoo.com

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to