Thank you, Antonio, I didn't think on that option, why is it better than having nine modules? on the other side, is it possible to specify that packaging for one module is just to compile (leave the .class files on the target) since packaging for each platform will be just one jar. How is it managed by maven? Best regards. Javier arias.
________________________________ From: Antonio Petrelli <[email protected]> To: Maven Users List <[email protected]> Sent: Fri, November 26, 2010 10:23:29 AM Subject: Re: multi-platform multi-module project/modules structure 2010/11/24 Javier Arias <[email protected]>: > So, here are my questions, I am new to maven, so some options may be just wong: > + which would be the best project structure? > - nine independent projects and two sepparate projects for the building? > - three projects dividing by platform?(eg. cross-platform, j2me, j2se) > each one with three modules? (frontend, commons, backend) > - only one project with nine modules and two different build targets? > + what are the best practices for this kind of problem? None of the above :-D I suppose that you want to maintain and release them at the same time. So create a project with: 1. the three crossplatform modules; 2. two modular modules, one for each platform, containing the specific j2se/j2me modules plus an assembly module. Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
