[ 
https://jira.codehaus.org/browse/MNG-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=336628#comment-336628
 ] 

pankaj gupta commented on MNG-5541:
-----------------------------------

They tried to debug the things and provided different solutions but didn't 
work. I am giving their ticket reference. Also I tried build with maven 2 and 
maven 3 but maven2 gives wagon-ftp and plexus artifact not found error at first 
place and if I commented out that code, it start giving error related to 
maven-clean-plugin. 

lease check and give me some input to resolve this issue asap. 

https://support.sonatype.com/requests/3343

https://support.sonatype.com/requests/3274

mvn --version ouput .

[appserv@lou-devbb01 wagon]$ mvn --version
Maven version: 2.0.9
Java version: 1.5.0_15
OS name: "linux" version: "2.6.32-358.18.1.el6.x86_64" arch: "amd64" Family: 
"unix"


                
> Artifact are not getting downloaded from repository
> ---------------------------------------------------
>
>                 Key: MNG-5541
>                 URL: https://jira.codehaus.org/browse/MNG-5541
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>            Reporter: pankaj gupta
>            Priority: Critical
>         Attachments: allStaging-build.xml, pom.xml, REL35-LIB80-JOB1-145.log
>
>
> I was using bamboo server and nexus on single server and it was working fine. 
> Recently we shifted our bamboo server and nexus server to new machine. Now 
> both reside on different machine. So I changed my pom.xml to put nexus server 
> path and tried to run build.xml but everytime I am getting same error. I 
> contacted with bamboo and nexus both and they debug and found issue with 
> maven. 
> I am attaching all files here for reference. This is a very urgent issue from 
> past 12 days and it is holding our migration. Please look into this asap. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to