maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Rowlands <>
Subject Suggested best practice for arranging projects
Date Thu, 04 Oct 2007 02:56:50 GMT

I have the following scenario for a bunch of projects I wish to implement:

I have a "Web Project" which acts as a router for web services. It must
contain the web services configuration, the wsdl and the schemas relating
to the wsdl. It will contain the "endpoints" of the web service - which
will be routed to the other projects.

I have a project containing the implementation of the Web Service.

I have a project which is a client of the web service. It will need the
wsdl and schemas from the Web project. This project also needs to be
consistent with the Web Service implementation

I have a EAR project which will collect everything above (it's not that
important in this context).

The concerns I have is what is the best way to do the following:

1.  Keep the schemas and wsdl consistent between the Web Project and the
client project. They must be identical. The wsdl is needed for
documentation, the schema is needed to generate some Java code (using

2.  Ensuring the client project and implementation project stay with
consistent versions, and stay in sync with the Web Project.

Normally I would classpath-type things, but this situation is not really
applicable to classpaths. I'm not convinced the best way is to copy the
files during the build (or even if that is possible via Maven between

Any ideas would be appreciated!



Disclaimer: The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or other use
of, or taking of any action in reliance upon, this information by persons
or entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the material
from your computer.
Privacy: If you are responding to this email or providing personal
information to the SRO for the purposes of one of the Acts it administers,
such information is used only for the purpose for which it was collected
( administration of SRO legislation ) and is protected by the Information
Privacy Act 2000 and secrecy provisions contained in legislation
administered by SRO. It is not disclosed otherwise than in accordance with
the law. If you would like a copy of the SRO Privacy Policy please refer to
SRO website ( or contact SRO on 9628 0556 and request a

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message