-
Improvement
-
Resolution: Unresolved
-
Major
-
None
Im trying to use the maven server repository plugin as a normal maven repository among some other local repositories. As it seems now, the component (3.0.0-SNAPSHOT version) that is available in the plugin repository isnt used in the build. Maven complains that it cant find the specific version, instead it shows the other versions available in the other repositories.
[INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [INFO] Building Unnamed - [INFO] task-segment: [process-sources] [INFO] ------------------------------------------------------------------------ [INFO] [build-helper:parse-version {execution: parse-version}] [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Couldn't find a version in [1.0.0.0-SNAPSHOT, 1.0.0.0, 1.0.0.1, 3.0.0.0, 3.0.1.0] to match range [3.0.1.1-SNAPSHOT,3.0.1.1-SNAPSHOT] com.company:component.python:jar:null from the specified remote repositories: central (http://repo1.maven.org/maven2), development (file:///mmmm/mvn.repo/development), jenkins-repository (http://arusha:8090/plugin/repository/everything/), release-mirror (http://gomel/repository/release), release (file:///mmmm/mvn.repo/release)
But when I check the http://arusha:8090/plugin/repository/everything/com/company/component.python/ url I can see that the 3.0.1.1-SNAPSHOT/ folder is there and it contains the right files.
Im no maven expert, but could it be that the plugin does not output a com/company/component.python/maven-metadata.xml so maven knows that the version is available in that repository?
