The easiest way to deal with shared libraries is to make them their
own projects and have A and B both depend on them.
This will likely also make your projects more stable.
Sometimes (Web Services for example) projects do depend on artifacts
from other main modules but if two modules depend on a set of classes,
that is a good reason to build a library (JAR) project.
Ron
On 07/09/2010 3:55 AM, Goli wrote:
Hi
I have two maven projects. There are different modules in these projects
such as api, service and da.
I refer to these two projects as ProjectA and ProjectB to describe the
issue. ProjectA has an api module which is dependent to the ProjectB api
module.
Also ProjectB service module is dependent to the service module of ProjectA.
Now the problem is that when I want to release ProjectA, the dependency of
ProjectB api is old and when I release the ProjectB, the dependency of
ProjectA service is old. So, I cannot have the last release version
dependencies for the both projects at the same time.
Please help me how I can resolve this issue.
Thank you in advance.
Goli
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
