So to restate - this duplicates this jar on your system, correct? And as far as <scope> goes, couldn't that path be a variable that is pulled out of people's profile in their settings.xml?
We try to enforce installation instructions of various third party items. The use case I want to be prepared to solve is the one where someone is testing out a NEW version of some tool (say an appserver), they should be able to say in the profile, here is the new location and may scope could pick that up? Also, in what context is scope used? -----Original Message----- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 28, 2006 4:58 PM To: Maven Users List Subject: Re: Building and requiring jboss jars 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 <[EMAIL PROTECTED]> 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? > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
