On 5/30/07, Robert Dale <[EMAIL PROTECTED]> wrote:
Put the jars in your local repository - system scope should be avoided.
Indeed, avoid system scope. It makes your builds irreproducible.
Cheers
Jo
Put the jars in your local repository - system scope should be avoided.
In your parent pom.xml:
com.xyz
abc-parent
...
com.xyz
abc
3.5.1
...
in your modules' pom.xml:
com.xyz
abc-parent
...
junit
junit
...
Hi Damon,
First thing. If the 3rd party jars are not available in repositories, there
is no other solution than installing them in your repository manually and
generate/create a POM for them. Nothing to do about that.
You don't install a 3rd party jar by creating a new maven project for them
and
Hi,
I've spent all afternoon working on this but am stuck.. I am building
several wars that all depend on the same set of 3rd party jar files. I
could write a batch file to install the jars to my local repos and
then copy and paste the list of dependencies into each war. But what I
really want is
