slfan1989 opened a new pull request, #2014:
URL: https://github.com/apache/auron/pull/2014
### Which issue does this PR close?
Closes #2013
### Rationale for this change
Currently, when developing in IntelliJ IDEA, users need to manually select
both a Spark profile (e.g., `spark-3.5`) and a Scala profile (e.g.,
`scala-2.12`) to ensure correct compilation. This two-step configuration is
error-prone and can lead to compatibility issues if mismatched.
This change simplifies the workflow by automatically locking the Scala
version and compiler configuration when a Spark profile is selected.
### What changes are included in this PR?
1. **Scala version properties**:
- Spark 3.x profiles: `scalaVersion=2.12`, `scalaLongVersion=2.12.18`
- Spark 4.x profiles: `scalaVersion=2.13`, `scalaLongVersion=2.13.17`
2. **scala-maven-plugin configuration**:
- Spark 3.x: Added `semanticdb-scalac` + `paradise` compiler plugins
- Spark 4.x: Added `-Ymacro-annotations` args + `semanticdb-scalac`
plugin (without paradise)
- Used `combine.self="override"` to prevent configuration merging with
base settings
### Are there any user-facing changes?
Yes. Users now only need to select a Spark profile (e.g., `spark-3.5`) in
IDEA, and the corresponding Scala version will be automatically configured. No
need to manually select separate `scala-2.12` or `scala-2.13` profiles.
### How was this patch tested?
Verified in IntelliJ IDEA by:
1. Selecting only `spark-3.5` profile → Scala 2.12.18 correctly configured
2. Selecting only `spark-4.0` profile → Scala 2.13.17 correctly configured
3. No need to select separate `scala-2.12` or `scala-2.13` profiles
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
