I think the MAVEN best practice is to set up a corporate repository
with the specific jars and then add that repo to your project pom.
If you're just trying to make it work, and don't mind checking Jars
into your code versioning system, then you could perhaps use the
<scope>system</scope> and <systemPath> settings to make those jars
available to the project without the trouble of setting up your own
Maven repo.
<dependency>
<groupId>aaa</groupId>
<artifactId>bbb</artifactId>
<version>1.0.1</version>
<scope>system</scope>
<systemPath>${basedir}\lib\aaa-bbb-1.0.1.jar</systemPath>
</dependency>
Wayne
On 3/16/06, Szczepan Faber <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What is the best practice in case of dependencies that are not hosted
> anywhere?
>
> Should jars land in project's 'lib' dir? A mojo should install jar
> into user's local repository? I assume that maven methodology requires
> me to create corporate / team wide repository with those specific
> jars...
>
> Thanks,
> Szczepan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
