Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11886#issuecomment-213800102
Jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12565
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12633#discussion_r60832575
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/views.scala ---
@@ -85,68 +88,74 @@ case class CreateViewCommand(
} else {
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12565#issuecomment-213798713
OK I'm going to merge this since they have been passing for the past 3 runs.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12622
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8741
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11803
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12111
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8195
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8972
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10761
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10419
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11201
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7647
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9490
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/11003
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12442
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12613#issuecomment-213798398
cc @zsxwing
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12622#issuecomment-213797832
Ok - this is good for now. I'll merge this PR and we can revisit this if we
have a better repro.
---
If your project is set up for it, you can reply to this email
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12636#issuecomment-213797642
cc @yhuai
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12635#issuecomment-213797600
cc @yhuai
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12634#issuecomment-213797489
**[Test build #56805 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56805/consoleFull)**
for PR 12634 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12634#discussion_r60832345
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/CatalystConf.scala ---
@@ -32,6 +32,8 @@ trait CatalystConf {
def
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12637
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213796049
LGTM merging in master.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12626#discussion_r60832189
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/TreeNode.scala
---
@@ -71,7 +71,9 @@ object CurrentOrigin {
}
}
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-213795843
That sounds good to me. No problem!
I'll update today.
Thank you, @srowen !
---
If your project is set up for it, you can reply to this email and have
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/12622#issuecomment-213795814
JVM addShutdownHook is being added for a couple for things and they have
logging, for example:
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/12621#issuecomment-213790118
That's odd. Will do that today.
_
---
If your project is set up for it, you can reply to this
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12626#discussion_r60831742
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/TreeNode.scala
---
@@ -71,7 +71,9 @@ object CurrentOrigin {
}
}
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/12621#issuecomment-213789465
@felixcheung I just noticed that DataFrame.R (the diff for which didn't
show up) has a bunch of roxygen comments of the form `SparkSparkDataFrame` --
Could you send a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213784744
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213784751
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213784113
**[Test build #56804 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56804/consoleFull)**
for PR 12640 at commit
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/12619#discussion_r60830595
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetQuerySuite.scala
---
@@ -589,6 +590,30 @@ class ParquetQuerySuite
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12639#issuecomment-213766679
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12639#issuecomment-213766683
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12639#issuecomment-213766057
**[Test build #56802 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56802/consoleFull)**
for PR 12639 at commit
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213764953
I ran the simple benchmark in JIRA:
```
sc.parallelize(0 until 1e4.toInt, 1).map { i =>
(i, Vectors.dense(Array.fill(1e6.toInt)(1.0)))
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213763628
**[Test build #56804 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56804/consoleFull)**
for PR 12640 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213757582
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213757581
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213757580
**[Test build #56803 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56803/consoleFull)**
for PR 12640 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12640#issuecomment-213757486
**[Test build #56803 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56803/consoleFull)**
for PR 12640 at commit
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/12640
[SPARK-14850][ML] specialize array data for VectorUDT/MatrixUDT
## What changes were proposed in this pull request?
This PR adds `IntArrayData` and `DoubleArrayData`, so that we don't
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-213756370
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-213756371
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-213756118
**[Test build #56800 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56800/consoleFull)**
for PR 12618 at commit
Github user lw-lin closed the pull request at:
https://github.com/apache/spark/pull/12638
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12639#issuecomment-213747697
**[Test build #56802 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56802/consoleFull)**
for PR 12639 at commit
Github user tedyu commented on the pull request:
https://github.com/apache/spark/pull/12639#issuecomment-213747456
@davies
Please take a look
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user tedyu opened a pull request:
https://github.com/apache/spark/pull/12639
[SPARK-14856] Correct message in assertion for 'returning batch for wide
table'
## What changes were proposed in this pull request?
There was a typo in the message for second assertion in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11956#issuecomment-213744591
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11956#issuecomment-213744592
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11956#issuecomment-213744589
**[Test build #56801 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56801/consoleFull)**
for PR 11956 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11956#issuecomment-213744416
**[Test build #56801 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56801/consoleFull)**
for PR 11956 at commit
Github user tedyu commented on a diff in the pull request:
https://github.com/apache/spark/pull/12619#discussion_r60828879
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetQuerySuite.scala
---
@@ -589,6 +590,30 @@ class ParquetQuerySuite
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213744110
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213744112
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213744050
**[Test build #56799 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56799/consoleFull)**
for PR 12637 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-213743088
@hvanhovell It is ready to review. Thanks!
This is partially related to what we discussed in
https://github.com/apache/spark/pull/12537
---
If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12618#issuecomment-213743041
**[Test build #56800 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56800/consoleFull)**
for PR 12618 at commit
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12618#discussion_r60828506
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalog.scala
---
@@ -78,29 +78,66 @@ class SessionCatalog(
Github user pravingadakh commented on the pull request:
https://github.com/apache/spark/pull/12420#issuecomment-213742826
@jkbradley I'll update the PR accordingly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-213740678
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-213740674
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-213739995
**[Test build #56798 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56798/consoleFull)**
for PR 12638 at commit
Github user pravingadakh commented on a diff in the pull request:
https://github.com/apache/spark/pull/12416#discussion_r60827833
--- Diff:
mllib-local/src/main/scala/org/apache/spark/ml/linalg/Matrices.scala ---
@@ -154,11 +172,12 @@ sealed trait Matrix extends Serializable {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213726228
**[Test build #56799 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56799/consoleFull)**
for PR 12637 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12638#issuecomment-213726229
**[Test build #56798 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56798/consoleFull)**
for PR 12638 at commit
GitHub user lw-lin opened a pull request:
https://github.com/apache/spark/pull/12638
[SPARK-14874][SQL][Streaming] Cleanup the useless Batch class
## What changes were proposed in this pull request?
The `Batch` class, which had been used to indicate progress in a stream,
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213726045
Jenkins retest this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213725950
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213725832
**[Test build #56797 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56797/consoleFull)**
for PR 12637 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213725948
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213725055
This looks correct to my eyes. The Since annotation is in place as a
non-test class; the existing test classes are moved into the test source root.
The parent pom now
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12416#discussion_r60827197
--- Diff:
mllib-local/src/main/scala/org/apache/spark/ml/linalg/Matrices.scala ---
@@ -154,11 +172,12 @@ sealed trait Matrix extends Serializable {
*
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213723361
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213723359
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213723024
**[Test build #56796 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56796/consoleFull)**
for PR 12416 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12571#discussion_r60826861
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
---
@@ -66,12 +66,20 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-213713219
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-213713218
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12568#issuecomment-213712873
**[Test build #56794 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56794/consoleFull)**
for PR 12568 at commit
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12626#discussion_r60826489
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/trees/TreeNode.scala
---
@@ -71,7 +71,9 @@ object CurrentOrigin {
}
}
Github user cloud-fan commented on the pull request:
https://github.com/apache/spark/pull/12634#issuecomment-213707877
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/12634#discussion_r60826409
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/CatalystConf.scala ---
@@ -32,6 +32,8 @@ trait CatalystConf {
def
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12637#issuecomment-213706212
**[Test build #56797 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56797/consoleFull)**
for PR 12637 at commit
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12637#discussion_r60826170
--- Diff:
examples/src/main/java/org/apache/spark/examples/mllib/JavaStratifiedSamplingExample.java
---
@@ -37,22 +37,19 @@ public static void main(String[]
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/12637
[SPARK-14873] [CORE] Java sampleByKey methods take ju.Map but with Scala
Double values; results in type Object
## What changes were proposed in this pull request?
Java `sampleByKey`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213704898
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213704897
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12560#issuecomment-213704837
**[Test build #56792 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56792/consoleFull)**
for PR 12560 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12636#issuecomment-213703072
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12636#issuecomment-213703073
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12636#issuecomment-213703028
**[Test build #56793 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56793/consoleFull)**
for PR 12636 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213700495
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213700473
**[Test build #56795 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/56795/consoleFull)**
for PR 12416 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12416#issuecomment-213700491
Build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/12631#issuecomment-213699239
Yes, on a system with Maven < 3.3.9 installed, you always have to pass
`--force`. This would at least make it optional on the second or subsequent
run.
201 - 300 of 392 matches
Mail list logo
