-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Bug] Maven deployment failed on project pulsar-presto-connector-original #17047
Comments
if you want to deploy again, you need to clean some generated resources first. |
How to clean them? Is there any guidance?
…---- Replied Message ----
| From | Qiang ***@***.***> |
| Date | 08/10/2022 23:52 |
| To | ***@***.***> |
| Cc | Yunze ***@***.******@***.***> |
| Subject | Re: [apache/pulsar] [Bug] Maven deployment failed on project pulsar-presto-connector-original (Issue #17047) |
if you want to deploy again, you need to clean some generated resources first.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I removed the whole project and it still failed. |
Run |
@BewareMyPower Yes. Although not in |
You may report this issue to MSHADE JIRA also. Maven is weak in incremental compilation, though. |
Yes, I also noticed it but I cannot reproduce it at the moment. |
This issue can be relevant elastic/apm-agent-java#961 |
Reported at upstream: https://issues.apache.org/jira/browse/MSHADE-425 It seems a maven shade plugin LTA. Or we may investigate to exclude some dependencies to workaround. |
I think I found the root cause. After the first run, we have both:
... in the path. And perhaps due to
CONFIRMED with customized logs:
This should be an upstream issue to resolve. As long as we hold the dependency and relocation logic, it's always there. We may try to get rid of the dependency of |
Here apache/maven-shade-plugin#150 is the fix for upstream. I've verified locally. Please react an emoji to prioritize it :) |
@BewareMyPower upstream fix is pending to release. You can assign this issue to me and I will do the upgrade after it's done. |
This closes apache#17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix. Signed-off-by: tison <wander4096@gmail.com>
This closes #17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix. Signed-off-by: tison <wander4096@gmail.com> Signed-off-by: tison <wander4096@gmail.com>
This closes #17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix. Signed-off-by: tison <wander4096@gmail.com> Signed-off-by: tison <wander4096@gmail.com> (cherry picked from commit 2865007)
This closes apache#17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix. Signed-off-by: tison <wander4096@gmail.com> Signed-off-by: tison <wander4096@gmail.com> (cherry picked from commit 2865007) (cherry picked from commit f53c9d5)
This closes #17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix.
This closes #17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix. Signed-off-by: tison <wander4096@gmail.com> Signed-off-by: tison <wander4096@gmail.com> (cherry picked from commit 2865007)
This closes #17047. Upstream patch is apache/maven-shade-plugin#150. Bump maven-shade-plugin version to 3.4.0 for the upstream fix. Signed-off-by: tison <wander4096@gmail.com> Signed-off-by: tison <wander4096@gmail.com> (cherry picked from commit 2865007)
Search before asking
Version
Pulsar branch-2.8
Minimal reproduce step
It has succeeded before. But it failed twice in a row when I tried to deploy it again. I have already removed the staging repository. See
Follow https://github.com/apache/pulsar/wiki/Release-process#5-stage-artifacts-in-maven (Apache Committer is required)
What did you expect to see?
mvn deploy
should succeed.What did you see instead?
Recently I encounted a problem when I ran the
mvn deploy
step inhttps://github.com/apache/pulsar/wiki/Release-process#5-stage-artifacts-in-maven.
We can see the previous artifacts were deployed successfully.
Anything else?
There were warning logs about the "overlapping resource"
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: