-
Notifications
You must be signed in to change notification settings - Fork 29k
[HOTFIX]: Fix maven build missing some class #3228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Test build #23268 has started for PR 3228 at commit
|
|
+1 looks correct to me, as other occurrences of this profile are activated by default in modules. It would also explain the behavior we see. |
|
Test build #23268 has finished for PR 3228 at commit
|
|
Test PASSed. |
|
See SPARK-4375 now. There is more to fixing it than this it seems. |
|
Currently there is no way around not passing -Pscala-2.10/-Pscala-2.11 for maven users. We can either document this, or I am not sure if there is another way. |
|
How about the following? <profile>
<id>scala-2.10</id>
<activation>
<property>
<name>scala.version</name>
<value>2.10.4</value>
</property>
</activation>
<properties>
<scala.binary.version>2.10</scala.binary.version>
<jline.version>${scala.version}</jline.version>
<jline.groupid>org.scala-lang</jline.groupid>
</properties>
<modules>
<module>external/kafka</module>
</modules>
</profile>
<profile>
<id>scala-2.11</id>
<activation>
<property>
<name>scala.version</name>
<value>2.11.2</value>
</property>
</activation>
<properties>
<scala.binary.version>2.11</scala.binary.version>
<jline.version>2.12</jline.version>
<jline.groupid>jline</jline.groupid>
</properties>
</profile> |
|
That still requires the user to set "scala.version", right? |
|
Yes, it seems to work.It seems that the user must explicitly set |
The bug was caused by #3159