-
|
@ronsigal I'm trying to build the main branch of this project locally but failed with the following errors: [INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'parent.relativePath' of POM dev.resteasy.grpc:grpc-tests:1.0.0.Alpha1-SNAPSHOT (/Users/weli/works/gRPCtoJakartaREST-archetype/arch-test/pom.xml) points at dev.resteasy.grpc:gRPCtoJakartaREST-archetype instead of dev.resteasy.grpc:resteasy-grpc-testsuite, please verify your project structure @ line 6, column 13
[FATAL] Non-resolvable parent POM for dev.resteasy.grpc:grpc-tests:1.0.0.Alpha1-SNAPSHOT: Could not find artifact dev.resteasy.grpc:resteasy-grpc-testsuite:pom:1.0.0.Alpha1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 6, column 13
@
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project dev.resteasy.grpc:grpc-tests:1.0.0.Alpha1-SNAPSHOT (/Users/weli/works/gRPCtoJakartaREST-archetype/arch-test/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for dev.resteasy.grpc:grpc-tests:1.0.0.Alpha1-SNAPSHOT: Could not find artifact dev.resteasy.grpc:resteasy-grpc-testsuite:pom:1.0.0.Alpha1-SNAPSHOT and 'parent.relativePath' points at wrong local POM @ line 6, column 13 -> [Help 2]
[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/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
[ERROR] Command execution failed.
org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)
at org.apache.commons.exec.DefaultExecutor.executeInternal (DefaultExecutor.java:404)
at org.apache.commons.exec.DefaultExecutor.execute (DefaultExecutor.java:166)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:1000)
at org.codehaus.mojo.exec.ExecMojo.executeCommandLine (ExecMojo.java:947)
at org.codehaus.mojo.exec.ExecMojo.execute (ExecMojo.java:471)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:972)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
at jdk.internal.reflect.DirectMethodHandleAccessor.invoke (DirectMethodHandleAccessor.java:104)
at java.lang.reflect.Method.invoke (Method.java:578)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)Do you have any suggestions on this? |
Beta Was this translation helpful? Give feedback.
Answered by
ronsigal
Aug 2, 2023
Replies: 4 comments 3 replies
-
|
Hmmm ... I just build the main branch with no problems ... |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Well, I have in arch-test/pom.xml. Looks like resteasy-grpc-testsuite is up to 1.0.0.Alpha2. I probably have a 1.0.0.Alpha1 sitting around and you don't, I'm thinking. Can you try updating to 1.0.0.Alpha2? |
Beta Was this translation helpful? Give feedback.
-
|
@ronsigal I modified the pom like this: ➤ git diff 00:32:29
diff --git a/arch-test/pom.xml b/arch-test/pom.xml
index 2c5c1f0..8bd0bb7 100644
--- a/arch-test/pom.xml
+++ b/arch-test/pom.xml
@@ -6,7 +6,7 @@
<parent>
<groupId>dev.resteasy.grpc</groupId>
<artifactId>resteasy-grpc-testsuite</artifactId>
- <version>1.0.0.Alpha1-SNAPSHOT</version>
+ <version>1.0.0.Alpha2</version>
</parent>
<properties>
<maven.compiler.parameters>true</maven.compiler.parameters>And now the error becomes: [INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 5.727 s
[INFO] Finished at: 2023-08-03T00:29:01+08:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project grpc-tests: Could not resolve dependencies for project dev.resteasy.grpc:grpc-tests:jar:1.0.0.Alpha2: The following artifacts could not be resolved: dev.resteasy.examples:grpcToRest.example.grpc:war:6.0.0-SNAPSHOT, dev.resteasy.examples:grpcToRest.example.grpc:jar:6.0.0-SNAPSHOT: Could not find artifact dev.resteasy.examples:grpcToRest.example.grpc:war:6.0.0-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public/) -> [Help 1]Seems it can't find: What additional steps should I fix this? |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
I think the problem is in gRPCtoJakartaREST-archetype/arch-test/pom.xml. Note that arch-script builds version 1.0.0.Final-SNAPSHOT, so that should be the version in arch-script. |
Beta Was this translation helpful? Give feedback.
Answer selected by
liweinan
-
|
@ronsigal Thanks for help! I have fixed the build process with your suggestions: 
I have submit a PR here: #8 Could you please help to check it? Thanks! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Thanks, Weinan!! You're really helping to work out the problems.
…On Wed, Aug 2, 2023, 1:30 PM 阿男 ***@***.***> wrote:
@ronsigal <https://github.com/ronsigal> Thanks for help! I have fixed the
build process with your suggestions :D
I have submit a PR here: #8
<#8> Could
you please help to check it? Thanks!
—
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEDP44E5J7MJ7NYU3OBEU3XTKFEXANCNFSM6AAAAAA3BNSLRU>
.
You are receiving this because you were mentioned.Message ID:
<resteasy/gRPCtoJakartaREST-archetype/repo-discussions/7/comments/6619358@
github.com>
|
Beta Was this translation helpful? Give feedback.
1 reply
-
|
My pleasure! :D |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think the problem is
in gRPCtoJakartaREST-archetype/arch-test/pom.xml. Note that arch-script builds