Skip to content

Conversation

@gh-yzou
Copy link
Contributor

@gh-yzou gh-yzou commented Jun 21, 2025

…857)"

This reverts commit 1f7f127.

The shadowJar plugin actually stops publish the original jar, which is not what spark client intend to publish for the --package usage.

Revert it for now, will follow up with a better way to reuse the shadow jar plugin, likely with a separate bundle project

Copy link
Contributor

@flyrain flyrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 on reverting it. We will need to revert it in 1.0 branch as well.

@github-project-automation github-project-automation bot moved this from PRs In Progress to Ready to merge in Basic Kanban Board Jun 21, 2025
@gh-yzou
Copy link
Contributor Author

gh-yzou commented Jun 21, 2025

@flyrain yes, once i got those the two PRs handled, i can take care of them together for 1.0

@eric-maynard eric-maynard merged commit f5871c5 into apache:main Jun 22, 2025
11 checks passed
@github-project-automation github-project-automation bot moved this from Ready to merge to Done in Basic Kanban Board Jun 22, 2025
flyrain pushed a commit that referenced this pull request Jun 23, 2025
)" (#1921)

…857)"

This reverts commit 1f7f127.

The shadowJar plugin actually stops publish the original jar, which is not what spark client intend to publish for the --package usage. 

Revert it for now, will follow up with a better way to reuse the shadow jar plugin, likely with a separate bundle project
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

Successfully merging this pull request may close these issues.

3 participants