HyukjinKwon commented on a change in pull request #27242: [SPARK-30534][INFRA] 
Use mvn in `dev/scalastyle`
URL: https://github.com/apache/spark/pull/27242#discussion_r368843858
 
 

 ##########
 File path: dev/scalastyle
 ##########
 @@ -17,18 +17,10 @@
 # limitations under the License.
 #
 
-SPARK_PROFILES=${1:-"-Pmesos -Pkubernetes -Pyarn -Pspark-ganglia-lgpl 
-Pkinesis-asl -Phive-thriftserver -Phive"}
+SCRIPT_DIR="$( cd "$( dirname "$0" )" && pwd )"
 
-# NOTE: echo "q" is needed because SBT prompts the user for input on 
encountering a build file
-# with failure (either resolution or compilation); the "q" makes SBT quit.
-ERRORS=$(echo -e "q\n" \
-    | build/sbt \
-        ${SPARK_PROFILES} \
-        -Pdocker-integration-tests \
-        -Pkubernetes-integration-tests \
-        scalastyle test:scalastyle \
-    | awk '{if($1~/error/)print}' \
-)
+SPARK_PROFILES=${1:-"-Pmesos -Pkubernetes -Pyarn -Pspark-ganglia-lgpl 
-Pkinesis-asl -Phive-thriftserver -Phive -Pdocker-integration-tests 
-Pkubernetes-integration-tests"}
+ERRORS=$($SCRIPT_DIR/../build/mvn $SPARK_PROFILES scalastyle:check | grep 
"^error file")
 
 Review comment:
   I would like to make a fix for SBT but wasn't able to reproduce. I removed 
all `.m2` and `.ivy2` but it still works and uses `[info] downloading 
https://repo1.maven.org/maven2`.
   
   If I am not wrong SBT uses HTTPs:
   
   
https://github.com/apache/spark/blob/a3357dfccacadfb40ab103ba1ff3c0927e806dd2/project/SparkBuild.scala#L227
   
   https://www.scala-sbt.org/0.13/docs/Resolvers.html
   
   So, I was wondering how to reproduce.

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to