Kogel, Jonck-van-der wrote: > Ok, allow me to rephrase :) I'm struggling with some proprietary (IBM, > Oracle, etc..) jars that I need to get added to my manifest class path. > I don't want to do that manually obviously. When I add the proprietary > jars to my pom and set their scope to default level, when I try to build > Maven complains that it can't find the proprietary jars in any of the > public repositories. I have added the jars to my local repository and > correctly set the directory structure to match my pom but to no avail. > So I googled and read that the way round that is to set the scope to > system. But then the jars don't get added to the manifest class path > anymore. So I guess my question is: how do I set it up so that Maven > only looks for proprietary jars on my local repository and doesn't try > to go outside and look for them?
Ideally you should run your own private repository and publish the jars there. At the most basic level, this repository is just a webserver, so it doesn't require much setup. This repository starts becoming important when you start using the release plugin to make your releases, your code will then be uploaded automatically to your same private repository. The core reason is that it's virtually guaranteed that someone else, on a different machine, will want to build you code, and if the jars are on a shared repository (public or private, maven does care), then this is trivial and automatic. Trying to maintain your own private directories of jars causes pain that maven steers you away from. Taking the effort to set up a private repo in the beginning will make your life significantly easier down the line. Regards, Graham --
smime.p7s
Description: S/MIME Cryptographic Signature
