Aha. Didn't think of that.
Thanks
Adam
Wayne Fay on 13/03/08 20:39, wrote:
You need to run mvn install again, and this time specify -DgeneratePom=true.
Then Maven will make an "empty" pom for the artifact such that it
won't go looking for it when you run mvn.
Wayne
On 3/13/08, Steve Chernyak
Hi Adam,
For each dependency, maven needs both a .jar and a .pom file. The .jar
file has the necessary code, and the pom file has the necessary
dependency info.
If you've installed only a jar into your local repository, maven will
still try to find the pom in the global repos.
The easiest soluti
You need to run mvn install again, and this time specify -DgeneratePom=true.
Then Maven will make an "empty" pom for the artifact such that it
won't go looking for it when you run mvn.
Wayne
On 3/13/08, Steve Chernyak <[EMAIL PROTECTED]> wrote:
> Did you try -o? "mvn -o install"
> -o = offline m
Did you try -o? "mvn -o install"
-o = offline mode.
On Thu, Mar 13, 2008 at 4:17 PM, Adam Hardy <[EMAIL PROTECTED]>
wrote:
> This question has possibly quite an easy answer, I hope.
>
> I manually installed a 3rd party jar into my local repository.
>
> Can I prevent mvn checking the global repos
This question has possibly quite an easy answer, I hope.
I manually installed a 3rd party jar into my local repository.
Can I prevent mvn checking the global repos whenever I run something?
It looks like marking it as scope="system" is one way but I don't want the
hassle of specifying a local
