Did this issue got resolved? I have a similar situation with 2 EJB modules depending on each other's ejb-client jar...
Since it's a legacy project, costs need to stay low and refactoring is no option.. Is it possible to manage the build of this project with maven 2? On 6/16/06, Lucas Opara <[EMAIL PROTECTED]> wrote:
Ok, It is bad I agree. But I want to know if there is a way to support cyclic references in Maven2. I have a project which contains Business Delegates classes. Those delegate classes can call EJB's remotely and locally. Thus I have a cyclic reference between my Delegate project and my EJB's project. As EJB's may call each other locally through the local delegates. -Lucas On 6/15/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > I would strongly suggest refactoring as this is bad > > -----Original Message----- > From: Lucas Opara [mailto:[EMAIL PROTECTED] > Sent: 15 June 2006 15:58 > To: [email protected] > Subject: Cyclic references in M2 projects > > Hello, > > I just migrated some of our J2EE projects to maven 2. > Now I have the problem with dependencies, with Maven telling me that I > have cyclic references between my projects. > Is it possible to handle those cyclic references or do I have to do some > refactoring? > > Eclipse just gives a warning when they are cyclic references, but it can > still compile the code in the right order. > Is Maven 2 capable of such a thing? > > Thanks, > > -Lucas > > Visit our website at http://www.ubs.com > > This message contains confidential information and is intended only > for the individual named. If you are not the named addressee you > should not disseminate, distribute or copy this e-mail. Please > notify the sender immediately by e-mail if you have received this > e-mail by mistake and delete this e-mail from your system. > > E-mail transmission cannot be guaranteed to be secure or error-free > as information could be intercepted, corrupted, lost, destroyed, > arrive late or incomplete, or contain viruses. The sender therefore > does not accept liability for any errors or omissions in the contents > of this message which arise as a result of e-mail transmission. If > verification is required please request a hard-copy version. This > message is provided for informational purposes and should not be > construed as a solicitation or offer to buy or sell any securities or > related financial instruments. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
