View Single Post
  (#1 (permalink)) Old
tvv2000 tvv2000 is offline
Member
 
Posts: 8
Thanks: 0
Thanked 0 Times in 0 Posts
Join Date: Apr 2008
Default Dependency management, why it's so difficult ? - 07-24-2008, 08:02 AM

Anybody could explain me why do you use maven. As I understand the main purpose of maven is a support of dependencies between modules/components in project. Other task such as reporting, documentation and others is not important. In this case it would be much more useful/simple to use less complicated tool. But it looks like there is no such one, I looked at Ant Ivy - it is simpler but for me it is not enough
As a developer I should provide two files for my module
  1. build.xml is used to build module
  2. module.xml describes module dependencies
For example module.xml describes dependencies in two scopes: production and test
HTML Code:
<module name="module1" version="1.2.3.4">
    <production>
        <dependency name="module3" version="1.2.3"/>
        <dependency name="module5" version="1.2.2"/>
        <dependency name="module7" version="1.2.12"/>
    </production>
    <test>
        <dependency name="module23" version="1.2.4"/>
        <dependency name="module27" version="1.2.9"/>
    </test>
</module>
If every module in project will provide such metainf it is very easy to create build.xml (for example it wiil contain a series of ant calls of build.xml for every component included into build) to build complete project. That is all what you need, no maven, no ivy - just simple tool.
What do you think, may be I too simplified a problem, I am not sure but I do not see any resons to use maven.
Reply With Quote