Maven proposes a default directory structure, with Java sources under "src/java", but as far as i know it's possible to customize Maven's defaults by declaring another sources directory in your "project.xml" file and by writing some Jelly script in a "maven.xml" file (to move source files from one directory to another in a preGoal for example...). I did it for a project in my company and it worked without any serious problem. I think you shouldn't adapt your project structure to Maven, but adapt Maven to your project structure and needs. Otherwise Maven can be considered as useless.
Philippe Curmin -----Message d'origine----- De : Erwin van der Koogh [mailto:[EMAIL PROTECTED] Envoyé : vendredi 30 janvier 2004 09:56 À : [EMAIL PROTECTED] Objet : Maven Hi guys, I have almost finished the move to Maven (maven.apache.org) of the entire codebase and website. Once this run is done I will upload the site to my webserver for people to take a look at.. it should be up at http://aalbes.hosting.west.nl/~erwin/xml-security Maven has some huge advantages.. it's dead-easy to generate a whole bunch of reports over the code.. metrics, unit tests and unit test coverage being the most important ones. It's a definate advantage to see those. Another advantage is that it's a hell of a lot easier to test different dependencies. There are 2 problems with it though.. one is that the xdoc dialect is slightly different that Forrest used, but I converted most of those.. That leaves the much bigger problem of it being next to impossible with the present directory layout.. To do this properly we would need to move all directories except C into a directory called java. This is something we would have wanted to do for a while (it makes a lot of sense), but are we prepared to do it? Considering CVS has no allowance of moving files and we would lose the history?.. I think the advantages outweigh the disadvantages, but what are other people's opinions? Erwin
