Hello all, I have never worked with maven before, but I have read about it and seems interesting. I have tested it with wicket, gwt, j2ee and webapp archetypes and I found that maven could be a huge time saver for the projects in the company I am working for. I have a particular project structure that I wish to migrate to maven. Currently I use ant for these. I read the documentation on goals, phases, pom, etc, and was hoping you could give me some ideas or show me the right path.
Here is a subset of my problem: I have three products that I am working on. A set of classes that help the developer fetch info from databases, manage configurations, etc. A set of classes that encapsulate communication with webservices. And a web application. Let's call them: - UtilLibraries - WSClients - WebApplication WebApplication uses UtilLibraries and WSClients. WSClients uses UtilLibraries as well. UtilLibraries just has some external dependencies like log4j. How should I organize these projects? Here is my idea: - each project should be created with its archetype on somedir/UtilLibraries, somedir/WSClients and somedir/WebApplication respectively - WebApplication's pom.xml should state that it depends on UtilLibraries and WSClients. WSClients' pom.xml should state that it depends on UtilLibraries - The directory somedir/ should be version controlled with, say, svn or cvs. - A developer checkouts somedir/ - If the developer wishes to develop on WebApplication, he should mvn install its dependencies in order to copy them in .m2/repositories What do you think? What is your experience with these kind of projects? I am pretty sure my idea is not maven-ish since I don't have any experience with this system. Thank you -- David Ojeda --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
