maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph <christoph.amsh...@fjh.com>
Subject Best practice: web service project structure
Date Tue, 10 Mar 2009 10:22:17 GMT

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
-- 
View this message in context: http://www.nabble.com/Best-practice%3A-web-service-project-structure-tp22431433p22431433.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message