The right/correct solution here is to setup an internal Maven repository where you deploy those jars to. It's been discussed so many times here by people trying to have an alternative solution blessed. There are other hackish ways to work around this, but you will then run into other issues. For sure.
For you internal repo you should get one of the free repository managers. You will install and have it set up in less than a day. Trying to work around this will cause you pain every day. /Anders On Tue, Jan 29, 2013 at 7:12 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Nooo. Please not that > > On Tuesday, 29 January 2013, Jeremy Long wrote: > > > One solution I've seen people use is outlined here: > > http://blog.dub.podval.org/2010/01/maven-in-project-repository.html > > > > --Jeremy > > > > On Tue, Jan 29, 2013 at 11:16 AM, Kristian Lind <klpc...@gmail.com > <javascript:;>> > > wrote: > > > > > Hi. I have a java project that uses maven. > > > I have some jar files that I want to use in the project, and they are > not > > > in maven repo. > > > Can I make a maven dependency to these jar files ? I do not have a > local > > > maven repo. > > > > > > Kris > > > > > >
