Hi Anshuman, Unfortunately, it does not work, actual location of packages is the project itself which is being built, and if I define the dependencies like you have mentioned, then it tries to look into the local repository and obiviously these dependencies does not exists in local repository and it comes out with an error.
Thanks for your help! Regards, Jaikumar -----Original Message----- From: Anshuman Srivastava [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 25, 2006 5:42 PM To: Maven Users List Subject: Re: [M2] : How to resolve package level dependencies Hi Jai i think you have to make an entry in pom.xml of project C for project D like this-- <dependency> <groupId>A.D</groupId> <artifactId>D</artifactId> <version>1.0</version> </dependency> Try it and let me know. Anshuman On 4/25/06, Sharma, Jaikumar <[EMAIL PROTECTED]> wrote: > > I have folder structure of the project : > > > |------Project A > | |-----sub-project B > | | > | |----|-------sub-sub project C > | | |-----------pom.xml > | |----|------sub-sub project D > | | |-----------pom.xml > | |-----pom.xml > |------pom.xml > > > In this scanario, packages access is defined in the classes, when I > compile sub-sub project C, it says package does not exist (which is > already there sub-sub project D) > > How to define dependency for this ? > > Thanks! > > Regards, Jaikumar > > > BM__MailAutoSig_________________________________________ > > > > Jaikumar Sharma > > Sr.Software Development Engineer > > > > Barco Control Rooms > > A-5, Sector - 5, > > Noida. India 201 301. > > Tel +91 120-2421-651 to 659 Ext.313 > > Fax+91 120 2421 691 > > <http://www.barco.com/> http://www.barco.com > > <mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED] > > _________________________________________ > > > - - - - - - - DISCLAIMER- - - - - - - - > Unless indicated otherwise, the information contained in this message > is privileged and confidential, and is intended only for the use of > the > addressee(s) named above and others who have been specifically authorized > to > receive it. If you are not the intended recipient, you are hereby notified > that any dissemination, distribution or copying of this message and/or > attachments is strictly prohibited. The company accepts no liability for > any > damage caused by any virus transmitted by this email. Furthermore, the > company does not warrant a proper and complete transmission of this > information, nor does it accept liability for any delays. If you have > received this message in error, please contact the sender and delete the > message. Thank you. > > - - - - - - - DISCLAIMER- - - - - - - - Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liablility for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
