Ask Your Question
1

Maven build fails on project features-base

asked 2015-02-05 00:46:48 -0700

bhavesh07 gravatar image

updated 2015-02-05 00:50:07 -0700

    [INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21:15.134s
[INFO] Finished at: Thu Feb 05 12:46:35 IST 2015
[INFO] Final Memory: 324M/494M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project features-base: Could not resolve dependencies for project org.opendaylight.controller:features-base:jar:1.5.0-SNAPSHOT: Could not find artifact org.ops4j.pax.exam:pax-exam-container-karaf:jar:3.0.0 in opendaylight-mirror (http://nexus.opendaylight.org/content/groups/public/) -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
edit retag flag offensive close merge delete

Comments

I'm also getting the same error. I sent a mail to controller-dev, no response yet.

Vishal Thapar ( 2015-02-05 00:53:14 -0700 )edit

They need to host 3.0.0 version which is currently missing in nexus.opendaylight.org.

faizan ( 2015-02-05 01:56:06 -0700 )edit

That is strange coz as per https://github.com/opendaylight/odlparent/commits/master/odlparent/pom.xml it should be 4.4.0

Vishal Thapar ( 2015-02-05 02:21:37 -0700 )edit

2 answers

Sort by ยป oldest newest most voted
2

answered 2015-02-05 19:56:43 -0700

Vishal Thapar gravatar image

This has been fixed by this commit: https://git.opendaylight.org/gerrit/#/c/14915

Do a git pull to get latest changes.

edit flag offensive delete publish link more
0

answered 2015-02-05 19:33:34 -0700

Abhishek gravatar image

Basically, the pom.xml listing in features-base is trying to pull in version 3.0.0 (which is provided it to it by the variable in the pom). You can try commenting that statement out in the pom and replacing it with an exact version that is present on Nexus. For example, try <version>4.4.0</version> and see if it works. Although I am not sure what problems may arise by using a higher level version for the same artifact. You could give it a shot.

edit flag offensive delete publish link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Question Tools

Follow
2 followers

Stats

Asked: 2015-02-05 00:46:48 -0700

Seen: 578 times

Last updated: Feb 05 '15