We will need to fix archiva, but for quick fix the only way I can suggest is to add a file:// URL to your maven.remote.repo propery and point to the repository where the EJB is deployed.
Nico. 2008/1/16, fabien.dubron <[EMAIL PROTECTED]>: > > > > nicolas de loof-3 wrote: > > > > 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. > > When the ear is built on the same host, there's no problem but the problem > is when other developers that don't have the ejb project in their > workspace > and have to download it from the repository on the server. > > Fabien. > -- > View this message in context: > http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14877657.html > Sent from the archiva-users mailing list archive at Nabble.com. > >
