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.
To quick Fix, you should rename the deployed directory to the "jars"
expected by archiva.
Nico.
2008/1/15, fabien.dubron <[EMAIL PROTECTED]>:
>
>
>
> nicolas de loof-3 wrote:
> >
> > What is the physical name for the deployed ejb jar ? It should be
> > EjbXX.jar
> > How did you deploy it on your managed repository ?
>
> /myrepository/myGroupId/ejbs/EjbPFE-0.5-beta-2.jar
>
> I deployed it with the maven "multiproject:deploy" command.
>
> Fabien.
> --
> View this message in context:
> http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14842719.html
> Sent from the archiva-users mailing list archive at Nabble.com.
>
>
