Building and requiring jboss jars

[EJ Ciramella <ej...@upromise.com>]

Hello again, I have a quick question about building with things like
jboss/weblogic.
 
So if the developer requires an appserver specific jar in their
classpath for a particular maven build, how does that get in the
.m2/repository directory?
 
In the ant world, we'd have created a classpath pointing to the location
of the jboss/weblogic installation directory and included "lib" or what
not.
 
What I don't want is watching maven copy down jars that already exist on
the system (or moving those from the jboss dir to the .m2/repository
directory).
 
Any thoughts guys?

Re: Building and requiring jboss jars

[Wayne Fay <wa...@gmail.com>]

You can use <scope>system</scope> with a
<systemPath>/your/file/path/here.jar</systemPath> in that dependency.
However this is not portable, as every developer could potentially
have that jar in a different place in their file system, so good luck
maintaining it.

As I've said before, I really don't suggest scope system. Its very
easy to use install:install-file to install the Jar into your local
Maven repo and use "normal" scopes like provided etc. So I generally
suggest that approach instead.

Wayne

On 4/28/06, EJ Ciramella <ej...@upromise.com> wrote:
> Hello again, I have a quick question about building with things like
> jboss/weblogic.
>
> So if the developer requires an appserver specific jar in their
> classpath for a particular maven build, how does that get in the
> .m2/repository directory?
>
> In the ant world, we'd have created a classpath pointing to the location
> of the jboss/weblogic installation directory and included "lib" or what
> not.
>
> What I don't want is watching maven copy down jars that already exist on
> the system (or moving those from the jboss dir to the .m2/repository
> directory).
>
> Any thoughts guys?
>
>