You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jan Palmquist (JIRA)" <ji...@codehaus.org> on 2008/02/08 16:30:35 UTC
[jira] Created: (MNG-3390) Plugin resolution/download fails for
plugins previously not downloaded if pom is unavailable
Plugin resolution/download fails for plugins previously not downloaded if pom is unavailable
--------------------------------------------------------------------------------------------
Key: MNG-3390
URL: http://jira.codehaus.org/browse/MNG-3390
Project: Maven 2
Issue Type: Bug
Components: Plugins and Lifecycle
Affects Versions: 2.0.8
Reporter: Jan Palmquist
Plugin download fail when running a plugin goal of a plugin previously not used.
I have successfully reproduced this problem using both eclipse and help plugin, so I assume it is not plugin related.
Scenario 1:
1. Delete (rename) ~/.m2/repository forcing everything to be downloaded from scratch
2. Change to a folder containing a pom.xml
3. Run mvn help:describe -Dplugin=versions
- will work
4. Change to a folder not containing a pom.xml
- will work
Scenario 2:
1. Remove (rename) your ~/.m2/repository
2. Change to a directory not containing a pom.xml file
3. Run mvn help:describe -Dplugin=help
- will not work, the help plugin can not be found!
- repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file
- central blacklisted
4. Change to a folder containing a pom.xml file
5. Run mvn help:describe -Dplugin=help
- will not work!
- the error is permanent, maven seems to cache failed attempts and will not try again until repos timeout has passed, or -U is supplied...
5. Run mvn help:describe -Dplugin=help -U
- will work
6. Change to a folder not containing a pom.xml
7. Run (omitting -U) mvn help:describe -Dplugin=help
- will work
The above scenarios will work correspondingly running e.g. mvn eclipse:add-maven-repo -Declipse.workspace=.
My problem is that my company use an installation guide used by many developers executing the latter command as part of their initial development environment set up, and often they have not yet been using the eclipse plugin prior submitting the command since their environment is completely new...
I do not know how to categorize the issue, nor prioritizing it, but it is for sure an annoyance for unexperienced maven users, particularily since maven, after the first failing attempt, will not try to download the plugin again...
--
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
[jira] Closed: (MNG-3390) Plugin resolution/download fails for
plugins previously not downloaded if pom is unavailable
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-3390.
-----------------------------
Assignee: Brett Porter
Resolution: Cannot Reproduce
the second case works for me.
What I expect is the case is that you have no access to the external repository, but an internal repo is declared in the POMs you use.
You should look at declaring your internal repo in settings.xml instead.
> Plugin resolution/download fails for plugins previously not downloaded if pom is unavailable
> --------------------------------------------------------------------------------------------
>
> Key: MNG-3390
> URL: http://jira.codehaus.org/browse/MNG-3390
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
> Affects Versions: 2.0.8
> Reporter: Jan Palmquist
> Assignee: Brett Porter
>
> Plugin download fail when running a plugin goal of a plugin previously not used.
> I have successfully reproduced this problem using both eclipse and help plugin, so I assume it is not plugin related.
> Scenario 1:
> 1. Delete (rename) ~/.m2/repository forcing everything to be downloaded from scratch
> 2. Change to a folder containing a pom.xml
> 3. Run mvn help:describe -Dplugin=versions
> - will work
> 4. Change to a folder not containing a pom.xml
> - will work
> Scenario 2:
> 1. Remove (rename) your ~/.m2/repository
> 2. Change to a directory not containing a pom.xml file
> 3. Run mvn help:describe -Dplugin=help
> - will not work, the help plugin can not be found!
> - repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file
> - central blacklisted
> 4. Change to a folder containing a pom.xml file
> 5. Run mvn help:describe -Dplugin=help
> - will not work!
> - the error is permanent, maven seems to cache failed attempts and will not try again until repos timeout has passed, or -U is supplied...
> 5. Run mvn help:describe -Dplugin=help -U
> - will work
> 6. Change to a folder not containing a pom.xml
> 7. Run (omitting -U) mvn help:describe -Dplugin=help
> - will work
> The above scenarios will work correspondingly running e.g. mvn eclipse:add-maven-repo -Declipse.workspace=.
> My problem is that my company use an installation guide used by many developers executing the latter command as part of their initial development environment set up, and often they have not yet been using the eclipse plugin prior submitting the command since their environment is completely new...
> I do not know how to categorize the issue, nor prioritizing it, but it is for sure an annoyance for unexperienced maven users, particularily since maven, after the first failing attempt, will not try to download the plugin again...
--
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