Hello again, I'm sorry to annoy you again but this is a realy urgent issue. Does anybody know why the dependencies are being resolved as described?
Thanks for any help! Regards, Thomas On Jan 24, 2008 4:19 PM, Thomas Tardy <[EMAIL PROTECTED]> wrote: > I forgot to say, that the EAR Libraries in the XxxEjb project are not > being exportet. Therefore it's surprising me why the XxxTest project can see > these Jars. > > > On Jan 24, 2008 3:57 PM, Thomas Tardy < [EMAIL PROTECTED]> wrote: > > > Hello, > > > > first of all, I have to explain the project structure. > > > > *XxxEar*: Eclipse Ear Project > > Contains all JARs > > No Maven build. > > Contains a Jar of the XxxCommon Project > > > > *XxxEjb*: Eclipse Ejb Project > > Contains the Ejbs. Gets the dependencies from the EAR Libraries. > > Maven dependencies for compile time. > > Uses the EAR Dependecy of the XxxCommon Project. > > > > *XxxCommon*: Eclipse Java Project > > Contains some utility classes. > > Maven dependencies. > > > > *XxxTest*: Eclipse Java Project > > Contains test classes. > > Maven dependencies to XxxCommon and XxxEjb for remote testing. M2Eclipse > > resolves both projects as project dependencies > > > > The problem I have is that the XxxTest Projects gets the classes from > > the XxxCommon project not directly from project? The classes from the Jar in > > the XxxEar Project are being used. > > > > Does anybody know why the behavior is like I described? How can I change > > it? > > > > Thanks for your help! > > Thomas > > > >
