At 12:13 PM 7/3/2003 -0500, you wrote:
Thanks for your comments, however I'm afraid this is not the problem we are
having.
I already have a local repository setup in addition to the ibiblio, the
trouble is that there are a couple of Jars that I'm not allowed to put in
there. Developers have to download the jars for themselves from oracle
after agreeing to a licence.
What I'm looking for is a way to provide information to a developer along
the lines of:
WARNING:
oraclesdo-1.0.jar cannot be downloaded automaticaly please obtain it from
http://oracle.com/foo/jars and install it into your local meven repository
under oracle/jars and try building again.
If this was just an inhouse project then yes, I could just put the jars on
our local server, but this is a distributed project so all the developers
will need to do this step.
Cheers
James
It is possible to use a 'local' repository AND the ibiblio repository
simultaneously
In our case, we use a local repository called 'http://supportweb/maven'
Below is a segment of our project.properties file. This allows us to
deploy to our site, yet draw from both.
# ---
# -- Repository for resolving dependencies (JAR, etc)
# ---
# -- maven.repo.central (Opt) Host of central repository in which
# project Artifacts are deployed
(released)
# Default=login.ibiblio.org
# -- maven.repo.central.directory(Opt) Directory on central repository in
which
# project Artifacts are deployed
(released)
# Default=/public/html/maven
# ---
# -- maven.repo.remote (Opt) Defines the main repository(s) for
dependencies
# Default=http://www.ibiblio.org/maven/
# -- maven.repo.remote.enabled (Opt) On-Line mode
# Default=true
# ---
# -- maven.repo.local(Opt) Local cache of all published
dependencies
# Default=${MAVEN_HOME}/repository
# ---
# -- maven.jar.override = on (Opt) There are two type of JAR override
directives.
# (1) to specify a specific JAR
artifact path
# for a given artifactId
# (2) specify a specific version of a
JAR
# artifact that exists in your
local repository.
# Default=http://www.ibiblio.org/maven/
# ---
# maven.jar.override = on (Opt) There are two type of JAR override
directives.
# maven.jar.a = ${basedir}/lib/a.jar # Jars set explicity by path.
# maven.jar.a = 1.0-beta-1# Jars set explicity by version.
# ---
maven.repo.remote=http://supportweb/maven/,http://www.ibiblio.org/maven/
# ---
maven.repo.central=supportweb
maven.repo.central.directory=/share/web/Website-Static/maven
-Original Message-
From: James Macgill [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 03, 2003 12:09 PM
To: [EMAIL PROTECTED]
Subject: current mechanism for non-distributable jars
Hi
I'm about to add code to the project which I work on which depends on jars
which can't be re-distributed by us. (Some Oracle drivers that are free to
download, but only from Oracle directly)
I remember that in the past Maven supported a file called:
non-distributable-jars.list which could be placed in the remote
repository. I have tried creating one of my own but with no noticeable
effect.
There seems to be no src file in the current cvs which makes any reference
to the file so I guess it is no longer supported.
Is there an alternative mechanism for informing a user that they need to
obtain a Jar themselves?
Any help/pointers would be appreciated
James
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
