I assume your client and server projects build separate JAR files? If there are intertwined code, you can have: project-core project-server project-client
Both project-server/project-client can have a dependency on project-core You can use parent POM or module poms to build http://stackoverflow.com/questions/1992213/maven-parent-pom-vs-modules-pom On Tue, May 3, 2011 at 1:05 PM, offbyone <[email protected]> wrote: > I am developing an extremely large project that has a separate build > procedure for the client and the server. Currently, the project is one > large project. I am currently using Ant, but would like to embrace maven. > > I understand that the "maven way" is to have a separate project per build, > but I am finding this very difficult to do since the code is fairly > intertwined. It will be very difficult if even possible for me to > completely separate the client code from the server code. This intertwined > dependency was a design decision which has resulted in code reuse. So I > don't see this as a bad design. > > I would really like to use maven, so what are my options? > > Is there no way to specify 2 builds in a single project? > > -- > View this message in context: > http://maven.40175.n5.nabble.com/multiple-project-builds-tp4368244p4368244.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- @tommychheng http://tommy.chheng.com
