org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > resolve dependencies for one or more projects in the reactor. Reason: Unable > to > > > get dependency information: Unable to read the metadata file for artifact 'com.sun.jersey:jersey-bundle:jar': Cannot find parent: com.sun.jersey:jersey-project for project: > null:jersey-bundle:jar:null > > > for project null:jersey-bundle:jar:null com.sun.jersey:jersey-bundle:jar:1.4 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), apache.snapshots.https ( https://repository.apache.org/content/repositories/snapshots), central (http://repo1.maven.org/maven2), apache.public.https ( https://repository.apache.org/content/repositories/public) Path to dependency: 1) org.apache.ranger:security-admin-web:war:0.4.0 at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via ranger-dev by Sitaraman Vilayannur, 1 year ago
Failed to > > resolve dependencies for one or more projects in the reactor. Reason: Unable > to > > > get dependency information: Unable to read the metadata file for artifact 'com.sun.jersey:jersey-bundle:jar': Cannot find parent
via apache.org by Unknown author, 1 year ago
Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at
via coderanch.com by Unknown author, 1 year ago
The packaging for this p roject did not assign a file to the build artifact at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:719) at
via osdir.com by Unknown author, 1 year ago
Unable to start the ServiceMix container at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719
via sourceforge.net by Unknown author, 1 year ago
Error installing artifact's metadata: Error while deploying metadata: Failed to transfer file: . Return code is: 400 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( DefaultLifecycleExecutor.java:703) at
via maven-wagon-users by Brett Porter, 1 year ago
Error deploying artifact: Failed to transfer file: http://continuum.td.foo.com/svn_repos/maven/snapshots/foo/engtools/pte/pte-web/1.0-SNAPSHOT/pte-web-1.0-SNAPSHOT.jar . Return code is: 409 at org .apache .maven .lifecycle
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to > > resolve dependencies for one or more projects in the reactor. Reason: Unable > to > > > get dependency information: Unable to read the metadata file for artifact 'com.sun.jersey:jersey-bundle:jar': Cannot find parent: com.sun.jersey:jersey-project for project: > null:jersey-bundle:jar:null > > > for project null:jersey-bundle:jar:null com.sun.jersey:jersey-bundle:jar:1.4 from the specified remote repositories: apache.snapshots (http://repository.apache.org/snapshots), apache.snapshots.https ( https://repository.apache.org/content/repositories/snapshots), central (http://repo1.maven.org/maven2), apache.public.https ( https://repository.apache.org/content/repositories/public) Path to dependency: 1) org.apache.ranger:security-admin-web:war:0.4.0 at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)

Users with the same issue

Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
Samebug visitor profile picture
Unknown user
Once, 5 months ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
28 more bugmates

Know the solutions? Share your knowledge to help other developers to debug faster.