On 11/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I am building an offline build, I want to verify the hold project is building in Maven on a disconnected machine. I copied my developer machine M2 repository to the isolated server.
I asked on IRC, and a local repository can't simply be copied and repurposed as a remote repository. Jason suggested looking at the 'repository-assembler' in the shared module, which can convert a local repo into a remote one by adding the missing metadata.
I think that I set up a repository for as an `internal' one. What is wrong with this ``~/.m2/setting.xml'' file? <url>file:/home/pilgripe/internal/maven-repository</url>
My file protocol urls have file:// then /path/to/whatever. So file:///home/... (with three /'s.)
from the specified remote repositories: central (http://repo1.maven.org/maven2), blah (file:/home/pilgripe/internal/maven-repository) Clearly the priority order of the repositories is incorrect, but how do you reorder them?
I don't think it's an option yet, nor is convincing Maven that certain groupIds are only ever going to be found in certain repositories. If you _never_ want Maven to contact the central repository, I think you'll need to configure something as a <mirrorOf> central and then take responsibility for making sure that repo has everything you need. I know you were playing with Archiva... that's the path I'd take. http://maven.apache.org/guides/mini/guide-mirror-settings.html -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
