Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/4876#issuecomment-77168087
Hmm.. I was trusting our effective pom trick was working properly. Forgot
the JIRA id for that though.
On Mar 4, 2015 6:10 PM, "Sean Owen" <[email protected]> wrote:
> @ScrapCodes <https://github.com/ScrapCodes> Right now, the published POMs
> are incorrect for Scala 2.11, because the parent POM defines
> scala.binary.version as 2.10, and child modules use that value to
> describe their dependencies. So the issue in this JIRA arises.
>
> Of course, the POM has a profile to switch this value for Scala 2.11. But
> this has no effect on how anyone consuming these POMs parse the POMs. They
> just read the default value instead that we've published for Scala 2.11.
> That is, when any tool (Maven etc) reads these POMs, they do so as if
> without any special flags, vars, profiles activated.
>
> So we also have to edit this value manually when making the 2.11 POM.
>
> It's not a problem with tools; the dependencies described by the Spark
> Scala-2.11 POMs are wrong as a result of this, and any tool that reads
them
> correctly reads the incorrect dependencies.
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/4876#issuecomment-77150739>.
>
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
