[
http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191997#action_191997
]
Eric Berry commented on MNG-4211:
---------------------------------
We've also seen this issue in 2.1.0, 2.2.0, and 2.2.1. We are using
Artifactory (2.0.8) as our maven proxy. We have Artifactory proxied behind
Apache using SSL. Here is a sample error we get from Maven, unfortunately (-X
is not turned on). This can happen with plugins or dependencies. The solution
is to rerun maven 1 or more times until the problem goes away.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] A required plugin was not found: Plugin could not be found - check that
the goal name is correct: File:
https://vmswdev1/artifactory/repo/com/ccadllc/firebird/maven/ccad-firebird-maven-flex-plugin/3.1.0-SNAPSHOT/ccad-firebird-maven-flex-plugin-3.1.0-SNAPSHOT.jar
does not exist
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=com.ccadllc.firebird.maven
-DartifactId=ccad-firebird-maven-flex-plugin -Dversion=3.1.0-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=com.ccadllc.firebird.maven
-DartifactId=ccad-firebird-maven-flex-plugin -Dversion=3.1.0-SNAPSHOT
-Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
com.ccadllc.firebird.maven:ccad-firebird-maven-flex-plugin:maven-plugin:3.1.0-SNAPSHOT
from the specified remote repositories:
central (https://vmswdev1/artifactory/repo)
com.ccadllc.firebird.maven:ccad-firebird-maven-flex-plugin:maven-plugin:3.1.0-SNAPSHOT
from the specified remote repositories:
central (https://vmswdev1/artifactory/repo)
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
> [regression] proxy access broken between maven version 2.0.10 and 2.1.
> Probably due to addition of wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: MNG-4211
> URL: http://jira.codehaus.org/browse/MNG-4211
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.1.0, 2.2.0
> Environment: WinXP SP2
> Reporter: Robert Glover Jr
> Priority: Blocker
> Fix For: 2.2.2
>
> Attachments: jira_files_4_total.zip
>
>
> At a large company, maven become impossible to use via proxy when maven
> upgraded from 1.0.10 to 2.1. maven has always worked fine via proxy in 2.0.9
> and continues to work fine. however maven via proxy always fails in version
> 2.1.0 and higher.
> Attached is a zip file containing 1) log of GMAIL chat between the
> creater of this JIRA and a maven developer. 2) two console outputs of
> running maven 2.2. RC3 showing the proxy failure messages. 3) setting.xml
> (with comments stripped out)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
