Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mvn clean package BUILD FAILURE #846

Open
lyl-244 opened this issue Jul 17, 2024 · 1 comment
Open

mvn clean package BUILD FAILURE #846

lyl-244 opened this issue Jul 17, 2024 · 1 comment

Comments

@lyl-244
Copy link

lyl-244 commented Jul 17, 2024

I'm using this project for the first time, when I do the step: mvn clean package, the terminal showing the following error, what should I do to fix it?

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:10 min
[INFO] Finished at: 2024-07-17T20:38:56+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.3.1:resources (default-resources) on project jpetstore: Execution default-resources of
goal org.apache.maven.plugins:maven-resources-plugin:3.3.1:resources failed: Plugin org.apache.maven.plugins:maven-resources-plugin:3.3.1 or one of its dependencies could not be resolved:
[ERROR]
[ERROR]
[ERROR] -> [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/PluginResolutionException

@harawata
Copy link
Member

Hello @lyl-244 ,

The CI builds are successful.
And I just ran ./mvnw clean package against master and the build was successful as well (macOS 14.5, JDK 17.0.6).

So, I don't see any problem on our end.
Here are a few advices.

  • You should try using the maven wrapper (./mvnw or mvnw.cmd) if you haven't.
  • It's unclear which dependency was not resolved, but there could be some temporary issue on the server side. If this is the case, the issue will be resolved within a few days, probably.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants