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 ----
In this way, jars come down from ibiblio, but jars that are not on ibiblio get put in a shared CVS location. I also override the local repo so that I can pull out multiple copies of this source tree (different brances, etc.), and the install tasks that try to install jars with the same version number do not interfere with each other. 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. since I am using the install tasks to move jars to my own local repo above. Steve Cheng wrote: >hello, I tried to set up a jar repository on a server in local LAN (instead of the >one in ibiblio), the setting is "maven.repo.remote = file:////myServer/jars", the >"myServer" has shared the "jars" directory to all PCS in the LAN. > >however, I kept getting the following error message when I run "maven java:jar" > >"....... java.lang.IllegalAccessError: already connected" > >I'm sure the network connectivity (as well as the sharing) is ok, cause I could >access it through NT explorer. So could someone give me some insights? > >Thanks in advance, >Steve > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
