Too me it sounds as the design of these projects isn't correct. As you've noticed when building, there's a circular dependency. You need to re-design IMO.
/Anders On Tue, Sep 7, 2010 at 09:55, Goli <[email protected]> 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 > -- > View this message in context: > http://maven-users.828.n2.nabble.com/maven-artifacts-nested-dependencies-tp5505537p5505537.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] > >
