Use something like:
<dependency>
<groupId>abc</groupId>
<artifactId>xyz</artifactId>
<version>1.0</version>
<scope>system</scope>
<systemPath>${basedir}/lib/abc-xyz-1.0.jar</systemPath>
</dependency>
However you are far better off simply using "mvn install:install-file"
to add the file to your local user repository! Scope system gives
strange results some times with dependencies...
Wayne
On 4/7/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> Declare it using a "system" dependency. Note the jar won't be packaged
> inside the project generated jar.
>
> On 4/7/06, Thomas Will <[EMAIL PROTECTED]> wrote:
> > I know it's not the usual or recommended case, but is
> > this possible somehow:
> >
> > I've got a web app, which has already a JAR in the
> > source directory under ....WEB-INF/lib
> > I do not want the JAR to be picked from the maven
> > repository, and thus I did not define the dependency.
> > How can I make that JAR (or better all existing JARs
> > in the WEB-INF/lib) visible to the compiler classpath?
> >
> > Tom
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Alexandre Poitras
> Québec, Canada
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
