Bug 13033

Created attachment 5059 [details]
pom.xml to reproduce the problem

Created attachment 5060 [details]
mvn output with error

I get that message when trying to build Ardor3D:
[ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.5: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.5 from/to central (http://repo.maven.apache.org/maven2): No connector factories available -> [Help 1]

It works when downloading and copying manually each missing pom file:
http://repo.maven.apache.org/maven2/org/sonatype/oss/oss-parent/7/oss-parent-7.pom

http://www.mail-archive.com/users@maven.apache.org/msg134044.html

Of course, this workaround isn't satisfying.

I uninstalled the packaged version of Maven. Now I use the zipped version (3.2.1) downloaded here:
http://maven.apache.org/download.cgi

and it works like a charm :)

I stumbled over the same problem.
After some digging I figured out that when additionally installing 

aether-connector-basic
aether-transport-wagon

the automatic download and installation of maven plugins into
$HOME/.m2/ works again.


However I'm not sure whether this is the final solution,
because when I install for example the maven-clean-plugin rpm
I would expect that mvn fetches this plugin from the local
hard disk. However, this plugins gets also downloaded from the
internet and installed separately into $HOME/.m2/ .

So, it seems that there is a problem with maven not being able 
to see its plugins that have been installed as rpms.

In general I consider it quite complicated to marry two packaging 
systems such as rpm and maven, which both have their own automatic 
ways of resolving the dependencies.
An easy solution could be to just provide the base maven 
package which pulls in the two packages mentioned above, so that 
maven can handle all of its dependency resolution itself.

CC: (none) => Michael.Riss

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD

Made only a short test, but it seems to work for me again in Mageia 5.
Thanks for the good work!