Apparently this needs to be well-documented somewhere on the Maven website, as this is a very common question on the User list...
Essentially, you cannot simply copy your local developer workstation repo to a directory on a server, expose it over HTTP, and call it a "Maven repo". A real Maven repo has additional metadata requirements etc that are created when you use install:install-file but only created with the deploy:deploy-file command. If you use the deploy:deploy-file (or another deploy command) to deploy your files, you will see the additional files created in the filesystem, and can compare the deploy repo to your local install repo. Or you can look at an artifact in your own ~/.m2/repository vs the same artifact in the www.ibiblio.org/maven2 repo. Wayne On 5/23/06, ben short <[EMAIL PROTECTED]> wrote:
I have the book allready but thanks all the same :) On 5/23/06, Mike Markovich <[EMAIL PROTECTED]> wrote: > Ben, Chris, here is a link to a free book on Maven. It looks pretty > good... > > > > http://www.mergere.com/common/reg.jsp?form_source=m-m2book&form_landing=defaultpage > > On Tue, 2006-05-23 at 11:34 +0200, Chris Eidhof wrote: > > Hi, > > > > I'm trying to create an internal repository. It should only contain > > some libraries that are specific to our project, and not part of > > IBiblio. What I've done, is this (probably not right, so correct me > > where I'm wrong): > > > > 0. Add those libraries (3d-party jars) with mvn install:install-file > > 1. Add them as dependencies to my pom.xml > > 2. mvn install does a build successful. > > > > I don't think every developer should do this, so what I want to do is > > share all those 3d-party libraries in an internal repository. I > > backed up my .m2 directory (and removed it), and this is what I did > > next. > > > > 1. Create a directory "custom-repos" on my webserver. > > 2. Recursively copied the directories from my local repository to my > > webserver (every custom library inside ~/.m2/repository) > > 3. Added the following line to my pom.xml: > > <repositories> > > <repository> > > <id>custom.repository</id> > > <name>My Custom Repository</name> > > <url>http://www.example.com/custom-repos/</url> > > </repository> > > </repositories> > > 4. mvn install > > > > Well, maven doesn't find or doesn't know how to interact with my > > custom repository. Can anyone give me a hint on what I'm doing wrong? > > > > Also, is there a naming convention for repository id's? I was > > thinking to use the package name of this project, something like > > com.example.project. > > > > Thanks in advance, > > Chris Eidhof > > > > > > > > --------------------------------------------------------------------- > > 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
