I suggest to you that you use maven-j2ee-archetype. I'm using it and it's great. If you need more help, let me know.
2009/9/23 Thomas Sundberg <thomas.sundb...@agical.com> > Hi! > > I'm about to set up en fresh project using Maven. It will contain a web > part > that will be a war, it will contain a ear part and it will contain > integration tests. How would you suggest organising it? > > I'm thinking on the lines of: > > root -- > -- ear [Mostly packaging for a application server] > > -- war -- src -- main -- java ... > -- test -- java ... [Unit test, not depending on any > external resources] > > -- integration-test -- src -- main -- java ... [Probably more or less > empty] > -- test -- java ... [All integration > tests needed, including > Selenium, > Database and similar stuff > that will > require a deployed and running application] > > It is likely that I will add more modules as the system expands. Each > module > will be self dependant regarding the unit testing and the Integration tests > will depend on these other modules. > > Do you have any suggestions that I want to consider with this set-up? > There might be more then one practise and probably more then one good > practise. There might not exist any best practise so I want to consider > more > then one set-up before I make up my mind. > > Best regards > Thomas > > -- > Thomas Sundberg > M. Sc. in Computer Science > > Agical AB > Västerlånggatan 79, 2 tr > 111 29 Stockholm, SWEDEN > > Mobile: +46 70 767 33 15 > E-mail: thomas.sundb...@agical.com > http://www.agical.com > Blog: http://thomassundberg.wordpress.com/ > -- "Computer science is not about computers any more than astronomy is about telescopes." E.W. Dijkstra (1930-2002)
