-
Notifications
You must be signed in to change notification settings - Fork 28.7k
Simplify build files for pipelines module #51089
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
Conversation
sql/pipelines/pom.xml
Outdated
</dependencies> | ||
<build> | ||
<outputDirectory>target/scala-${scala.binary.version}/classes</outputDirectory> | ||
<testOutputDirectory>target/scala-${scala.binary.version}/test-classes</testOutputDirectory> | ||
<plugins> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In fact, this plugin is also redundant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great to simplify – I just took this out.
project/SparkBuild.scala
Outdated
@@ -884,6 +886,36 @@ object SparkConnectClient { | |||
) | |||
} | |||
|
|||
object SparkDeclarativePipelines { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So far, it seems that SparkDeclarativePipelines
doesn't require any additional configuration. I changed it to
object SparkDeclarativePipelines {
lazy val settings = Seq()
}
and then executed build/sbt clean "pipelines/test"
. All the tests still passed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great - I just took this out.
I ended up including this inside the underlying PR, so now closing |
What changes were proposed in this pull request?
This is a followup PR to #51003, which removes extraneous elements from the sbt and Maven build files, as suggested by @LuciferYang.
Why are the changes needed?
Does this PR introduce any user-facing change?
No
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
No