Hi Tim, 

        thank you very much for your reply.

        The problem was due to your first suggestion. By simply adding
file:// to the url it worked.

        In retrospect I should have know this. Anyway, thank you again.

Regards,

Stefan 

-----Original Message-----
From: Tim Kettler [mailto:[EMAIL PROTECTED] 
Sent: 06 September 2007 12:15
To: Maven Users List
Subject: Re: Confused by local repository

Hi,

It's not entirely clear from your description if the build fails becauce

maven can't find the repository at all. Then this syntax might be what 
you want:

   <url>file://${basedir}/libs</url>

Or if it just fails to retrieve the artifact from the repository. In 
that case, remember that a valid remote repository (which your lib-repo 
is) must contain the correct metadata.xml files.

-Tim

KOULOURIS Stefan schrieb:
> Hi all,
>  
>     I'm trying to setup a project limited by a very restrictive
> repository management.
>  
>     Let's say we can't use the normal maven2 repo...only the
repository
> setup by the organisation in which only the approved libraries reside.
>  
>     This repository doesn't contain all the libs our project needs, so
> we somehow must manage those by ourselves.
>  
>     What I tried to do was add the following snippet to our projects
> pom.xml
>  
>     <repositories>
>         <repository>
>             <releases>
>                 <enabled>true</enabled>
>             </releases>
>             <snapshots>
>                 <enabled>true</enabled>
>             </snapshots>
>             <id>local</id>
>             <name>local</name>
>             <url>lib</url>
>         </repository>
>     </repositories>
>  
>     For me it means that the lib directory relative to the pom wil be
> used to lookup the missing jars.
>     
>     This lib directory is managed by cvs...So everyone checking out
the
> project should be able to run the Maven2 tasks.    
>  
>     So for example, if we have a dependency to gwt...it will first try
> to look it up in the remote repository. It won't find it so it now
> searches in the lib directory containing following structure:
> lib/gwt/gwt-user/1.4.60/gwt-user-1.4.60.jar
>      
>     <dependency>
>         <groupId>com.google</groupId>
>         <artifactId>gwt-user</artifactId>
>         <version>1.4.60</version>
>     </dependency>
>  
>     Eventhough the layout is ok I get following error message:
>  
>     Missing artifact 
>         com.google:gwt-user:jar:1.4.60
>         Try downloading the file manually from the project website.
>         Then, install it using the command: 
>         mvn install:install-file -DgroupId=com.google
> -DartifactId=gwt-user -Dversion=1.4.60 -Dpackaging=jar
> -Dfile=/path/to/file 
>  
>         Alternatively, if you host your own repository you can deploy
> the file there: mvn deploy:deploy-file -DgroupId=com.google
> -DartifactId=gwt-user -Dversion=1.4.60 -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -        repositoryId=[id]
> 
>        Path to dependency:
> 
>         1) ec.ep:project:war:1.0
> 
>         2) com.google:gwt-user:jar:1.4.60
> 
>  
>     from the specified remote repositories:
>         /*Our remote repo*/,
>         local (lib)
>  
>     Is there perhaps an option I forgot to use, or can't this be done
> like this.
>  
>     Any suggestions are highly appreciated.
>  
> Regards,
>  
> Stefan Koulouris
>  
> 


---------------------------------------------------------------------
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]

Reply via email to