--- Jose Gonzalez Gomez <[EMAIL PROTECTED]> wrote: > > Is this the recommended approach for j2ee > applications? I mean, I > was thinking about switching to maven because of all > the added > functionalities over ant (source code metrics, cross > reference source, > documentation and site generation using xdocs,...) > but if I have to > create a maven project for each artifact in my > application, I think that > this could become cumbersome for large j2ee > applications, so maybe I > would delay adopting maven as my main build tool.
It depends what tiers your application has. If it's only web tier, without EJB ( and produces single .war file ) then one maven project will be sufficient. With java code for your servlet/MVC framework, test cases and web sources. Though I would separate EJB tier into separate project, and build them together using reactor. I'm working on project which is a big portal with really different parts. So I move all stuff which can be used elsewhere ( like portlet management, persistence/business logic for applications which could be used from separate web context ) into separatreprojects, which produce deployment units ( like ejb-jar ) and client libraries. This wa I can distribute work on the project parts between my code velopers ( and sometimes our partner companies ) Then all tested versions of subsystem are integrated into portal project itself. Currently I got following projects: - validation framework - portlet management - persistence layer and business logic for application - integration project In future I plan to add some other projects and setup common reactor for integration builds. ( and come OS projects I'm using will be also integrated there. And if they do not have maven build system yet, I write it myself and try to lobby them to adopt it :) ) > any convention in order to be used by maven? What is > the relation > between maven.xml, build.xml, project.xml, > project.properties? maven xml defines your build goals ( and is mostly not necessary - not for standart cases ) build.xml is POABS ( plain old ant build script ), possibly generated by maven. project.xml defines projects tructure and dependencies project.properties allows fine tuning of goals defined by maven and your goals There is also build.properties which will override propject.properties and is used for user local settings ( do not check it in into CVS ) 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://platinum.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
