Can't your ear be built on the same host the ejb is built ? In such case the ejb is available in local repository and no archiva instance is required
Nico. 2008/1/16, fabien.dubron <[EMAIL PROTECTED]>: > > > > nicolas de loof-3 wrote: > > > > Looking at source code I've found : > > > > /* TODO: Re-enabled in the future. > > public void testGoodFooEjbClient() > > > > This is not directly your issue, but similar. > > > > Please report on Jira so that we don't forget to fix this. Few archiva > > developer still use maven1 (maybe I'm the only one) and none (AFAIK) use > > m1 > > layout for managed repositories. > > Ok, i'm going to report that problem on jira. > > > > nicolas de loof-3 wrote: > > To quick Fix, you should rename the deployed directory to the "jars" > > expected by archiva. > > > > Nico. > > I thought about that issue but the problem is that this dependency needs > to > be declared as ejb because it's included in an ear application and is > declared in the application.xml which is automatically generated... > > > Thanks for your help, > Fabien. > -- > View this message in context: > http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14875059.html > Sent from the archiva-users mailing list archive at Nabble.com. > >
