Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 2.2.x (to be reviewed)
-
Fix Version/s: 3.0-alpha-1
-
Component/s: Artifacts and Repositories
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
We can also have a secondary check to see that if a metadata file contains no valid versions to nuke it and try to download a valid one. This will correct anything left over from previous versions of Maven.
Issue Links
| This issue relates to: | ||||
| MNG-2408 | Improve handling of "no plugin version found" error after intermittent errors |
|
|
|
To reproduce (with 2.0.7):
mvn archetype:create -DgroupId=com.example -DartifactId=test
cd test
mvn install -Dmaven.repo.local=/path/to/tempdir -o
mvn install -Dmaven.repo.local/path/to/tempdir
Example plugin metadata file:
<?xml version="1.0" encoding="UTF-8" ?>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-resources-plugin</artifactId>
</metadata>
- build offline with clean local repo, which fails
mvn install -Dmaven.repo.local=/path/to/tempdir -o
- repeat build while online-- still fails
mvn install -Dmaven.repo.local/path/to/tempdir
Example plugin metadata file: <?xml version="1.0" encoding="UTF-8" ?>