If you plan to distribute Oracle's proprietary jars etc, make sure you have the proper licensing etc necessary to do so.
(These issues are exactly why these jars are not already available in the Maven repo.) Wayne On 5/31/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 5/31/07, SiSi'mon <[EMAIL PROTECTED]> wrote: > > Yes, we have already done this (downloaded an put in local repository) and > internally we are doing this in development. But we do not have the ability > to serve as a Maven2 repository to customers we ship to so when they run the > installer it will need to fetch the Oracle jars from somewhere. > > suggestions would be appreciated. We may need to ship the actual .jar in > the release and somehow tell maven to look at the lib/*.jars instead of > trying to fetch it from a repository. Maven can use filesystem based repositories (with file:// urls). You could create the repository structure as part of your build, add a <repository> element pointing to it to the pom, and then the build should work. I saw this done once... I think it was in the Celtix project. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
