[jira] [Commented] (SPARK-33106) Fix sbt resolvers clash
[
https://issues.apache.org/jira/browse/SPARK-33106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17266706#comment-17266706
]
Alexander Bessonov commented on SPARK-33106:
My bad. I had the following in my environment that caused the issue. Builds
fine without it.
{code:java}
SBT_OPTS="-Dsbt.override.build.repos=true"{code}
> Fix sbt resolvers clash
> ---
>
> Key: SPARK-33106
> URL: https://issues.apache.org/jira/browse/SPARK-33106
> Project: Spark
> Issue Type: Improvement
> Components: Build
>Affects Versions: 3.1.0
>Reporter: Denis Pyshev
>Assignee: Denis Pyshev
>Priority: Minor
> Fix For: 3.1.0
>
>
> During sbt upgrade from 0.13 to 1.x, exact resolvers list was used as is.
> That leads to local resolvers name clashing, which is observed as warning
> from SBT:
> {code:java}
> [warn] Multiple resolvers having different access mechanism configured with
> same name 'local'. To avoid conflict, Remove duplicate project resolvers
> (`resolvers`) or rename publishing resolve
> r (`publishTo`).
> {code}
> This needs to be fixed to avoid potential errors and reduce log noise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-33106) Fix sbt resolvers clash
[
https://issues.apache.org/jira/browse/SPARK-33106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17261694#comment-17261694
]
Denis Pyshev commented on SPARK-33106:
--
[~nonsleepr], could you please provide details on error you have observed?
Cause invoking such a command on master at this current moment doesn't throw it.
{code:java}
commit d00f0695b7513046e42e47f35b280d7aa494de5b (HEAD -> master,
upstream/master, origin/master, origin/HEAD)
Author: Chandni Singh Date: Fri Jan 8 12:21:56 2021
-0600
{code}
> Fix sbt resolvers clash
> ---
>
> Key: SPARK-33106
> URL: https://issues.apache.org/jira/browse/SPARK-33106
> Project: Spark
> Issue Type: Improvement
> Components: Build
>Affects Versions: 3.1.0
>Reporter: Denis Pyshev
>Assignee: Denis Pyshev
>Priority: Minor
> Fix For: 3.1.0
>
>
> During sbt upgrade from 0.13 to 1.x, exact resolvers list was used as is.
> That leads to local resolvers name clashing, which is observed as warning
> from SBT:
> {code:java}
> [warn] Multiple resolvers having different access mechanism configured with
> same name 'local'. To avoid conflict, Remove duplicate project resolvers
> (`resolvers`) or rename publishing resolve
> r (`publishTo`).
> {code}
> This needs to be fixed to avoid potential errors and reduce log noise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-33106) Fix sbt resolvers clash
[
https://issues.apache.org/jira/browse/SPARK-33106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17260903#comment-17260903
]
Alexander Bessonov commented on SPARK-33106:
That doesn't seem to fix the issue:
{code:java}build/sbt publishLocal{code} now seems to end with an error
"Undefined resolver 'ivyLocal'".
> Fix sbt resolvers clash
> ---
>
> Key: SPARK-33106
> URL: https://issues.apache.org/jira/browse/SPARK-33106
> Project: Spark
> Issue Type: Improvement
> Components: Build
>Affects Versions: 3.1.0
>Reporter: Denis Pyshev
>Assignee: Denis Pyshev
>Priority: Minor
> Fix For: 3.1.0
>
>
> During sbt upgrade from 0.13 to 1.x, exact resolvers list was used as is.
> That leads to local resolvers name clashing, which is observed as warning
> from SBT:
> {code:java}
> [warn] Multiple resolvers having different access mechanism configured with
> same name 'local'. To avoid conflict, Remove duplicate project resolvers
> (`resolvers`) or rename publishing resolve
> r (`publishTo`).
> {code}
> This needs to be fixed to avoid potential errors and reduce log noise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-33106) Fix sbt resolvers clash
[
https://issues.apache.org/jira/browse/SPARK-33106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212059#comment-17212059
]
Apache Spark commented on SPARK-33106:
--
User 'gemelen' has created a pull request for this issue:
https://github.com/apache/spark/pull/30006
> Fix sbt resolvers clash
> ---
>
> Key: SPARK-33106
> URL: https://issues.apache.org/jira/browse/SPARK-33106
> Project: Spark
> Issue Type: Improvement
> Components: Build
>Affects Versions: 3.1.0
>Reporter: Denis Pyshev
>Priority: Minor
>
> During sbt upgrade from 0.13 to 1.x, exact resolvers list was used as is.
> That leads to local resolvers name clashing, which is observed as warning
> from SBT:
> {code:java}
> [warn] Multiple resolvers having different access mechanism configured with
> same name 'local'. To avoid conflict, Remove duplicate project resolvers
> (`resolvers`) or rename publishing resolve
> r (`publishTo`).
> {code}
> This needs to be fixed to avoid potential errors and reduce log noise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Commented] (SPARK-33106) Fix sbt resolvers clash
[
https://issues.apache.org/jira/browse/SPARK-33106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17212058#comment-17212058
]
Apache Spark commented on SPARK-33106:
--
User 'gemelen' has created a pull request for this issue:
https://github.com/apache/spark/pull/30006
> Fix sbt resolvers clash
> ---
>
> Key: SPARK-33106
> URL: https://issues.apache.org/jira/browse/SPARK-33106
> Project: Spark
> Issue Type: Improvement
> Components: Build
>Affects Versions: 3.1.0
>Reporter: Denis Pyshev
>Priority: Minor
>
> During sbt upgrade from 0.13 to 1.x, exact resolvers list was used as is.
> That leads to local resolvers name clashing, which is observed as warning
> from SBT:
> {code:java}
> [warn] Multiple resolvers having different access mechanism configured with
> same name 'local'. To avoid conflict, Remove duplicate project resolvers
> (`resolvers`) or rename publishing resolve
> r (`publishTo`).
> {code}
> This needs to be fixed to avoid potential errors and reduce log noise.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
