I am currently overriding both the remote (adding my own local remote as well as keeping ibiblio) and the local repo by using values in the project.properties, as follows:
---- project.properties ----
# override remote repo since we want to also point to a cvs based remote repo
# to get some jars not found at ibiblio
maven.repo.remote=http://www.ibiblio.com/maven/,http://some.where/else/,file:${basedir}/../../shared/repository
# overrid local repo since we want to allow this set of related source projects
# to be built from multiple locations without conflicting
maven.repo.local=${basedir}/../mavenrepo
----

Note that maven.repo.central, where the deploy task will try to deploy to, will still be ibiblio in this example. This is ok for me. I am using the install tasks to move jars to my own local repo above.


Rademacher Tobias wrote:

Hi Folks,

in beta-7 in I was able to change the maven.repo.local and maven.repo.remote
values in order to configure new repositories. My current cvs snapshot, which is from last week, does not
longer contain driver.jelly or
driver.properties. As far as I know driver.properties has been used in
beta-7 to configure repositories.
Is this out of date? If so: Where I have to place the configuration know? If
it is not out of date: Where does maven
get the information know and can I simply overwrite it by creating a new
driver.properties file?

Thx for your advice and help

Bye
Toby

--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to