http://www.sonatype.com/books/maven-book/reference/
Have a look at the multi-module projects. Christoph wrote:
Hi, we're want to setup a couple of web service projects that have to provide several artifacts: * ws-client.jar: contains everything required to call the WS * ws-impl.jar: provides the implementation of a WS * ws-core.jar: contains base classes used by both of the others This way a WS client is not forced to have dependencies required for WS implementation. Quite common, I think. Now... the question is, how to best set this up with Maven. I didn't find very much in documentation and mailing lists about how to structure the projects. IMO there are two options: 1) Have a single Maven project that generates multiple artifacts (JAR files). They could all have the same base name but a distinct classifier, for instance. Assembly plugin could be useful, right? Of course, all JARs must be deployed in the end. 2) Use a multi-module project with dedicated subprojects for the 2 artifacts, so there is one artifact per Maven project. However, this might be some overhead because some projects will only contain few files. What do you think, which way is the preferred one? How are YOU doing WS projects? Thanks for any opinion, Christoph
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
