On Fri, 20 May 2005 [EMAIL PROTECTED] wrote:

> 1) Problem:
>
> We used the following in the build.properties file to download third
> party dependencies from a central repository (The central repository was
> setup in a Web server in a Linux machine). The download did not succeed.
>
>                         maven.repo.remote=http://10.145.92.29:8081/maven
>
> 2) Problem:
>
>             We used the following in the project.xml to download the
> commons-digester jar from the given URL, but it failed. Even in the
> below section the url refers to the central repository mentioned in
> Problem 1
>
>                         <dependency>
>
>                                     <groupId>commons-digester</groupId>
>
>
> <artifactId>commons-digester</artifactId>
>
>                                     <version>1.5</version>
>
>
> <url>http://10.145.92.29:8081/maven</url>
>
>                         </dependency>

The url only specifies where to look for the dependency if the download
fails, it is not used by maven to download it.

If you use your browser to go to
http://10.145.92.29:8081/maven/commons-digester, can you find the file
there? If it isn't there, try to add ibiblio to the maven.repo.remote
(comma separated list). I don't know if you want to mirror the jars you
need on your 'local' remote repository, but the problem clearly is that
the jar is not found there.

>
> 3) Problem:
>
>             We used the following in the build.properties file to deploy
> the artifacts to the central repository during the build process. Even
> in the below section the url refers to the central repository mentioned
> in Problem 1.
>
>                         maven.repo.list=wyndhamrepo
> maven.repo.wyndhamrepo=ftp://10.145.92.29
> maven.repo.wyndhamrepo.directory=/home/wynmgm/jakarta-tomcat-4.1.31/weba
> pps/maven/
> maven.repo.wyndhamrepo.username=wynmgm
> maven.repo.wyndhamrepo.password=wynmgm
>
>  Output:
>
>             The following error occurred:
>
> Will deploy to 1 repository(ies): wyndhamrepo
> Deploying to repository: wyndhamrepo

[snip]
> CWD /home/wynmgm/jakarta-tomcat-4.1.31/webapps/maven/
> 250 Directory successfully changed.
>
> Deploying:
> D:\MavenEx\sample-echo\sample-echo\project.xml-->sample/poms/sample-1.0.
> pom
>
> CWD sample
> 550 Failed to change directory.
> MKD sample
> 550 Create directory operation failed.
> Failed to deploy to: wyndhamrepo Reason: Error executing FTP command

This indicates some error on the server. It could be permission related.
Maybe there's more information in the log files of the ftp server?

Using a normal ftp client to do this will also not work, so this is really
not a maven problem, but an ftp server configuration problem.

> 4) Problem:
>
>             We used the same set of properties as mentioned in the above
> problem to deploy the artifacts to the central repository in a Windows
> machine using file protocol, but it failed to deploy the artifacts in
> the required central repository.

What went wrong there?

> Please provide us some solution to deploy artifacts in a central
> repository and download dependencies from central repository.

Downloading from a central repository should work, but you didn't give the
output of maven stating the failure, so I cannot help you there. It's
probably due to a 404; you should APPEND your internal remote repository
to the maven.repo.remote, not replace it, as it won't be able to find
any jars on ibiblio any more.


-- Kenney

>
> Regards,
>
>
>
> Vijay
>
>
>
>
>
> Confidentiality Notice
>
> The information contained in this electronic message and any attachments to 
> this message are intended
> for the exclusive use of the addressee(s) and may contain confidential or 
> privileged information. If
> you are not the intended recipient, please notify the sender at Wipro or 
> [EMAIL PROTECTED] immediately
> and destroy all copies of this message and any attachments.

--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

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

Reply via email to