[
https://issues.apache.org/jira/browse/SPARK-10037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699775#comment-14699775
]
Sean Owen commented on SPARK-10037:
-----------------------------------
Yes that looks right. You should be able to attach files from the "More" menu
(if logged in). But really, just have a look at what the profile declarations
look like in this modified pom.
Did you try "mvn dependency:tree" on your 2.11 build to see if perhaps jline is
coming in from somewhere else?
It would be a good lead if so, but still doesn't quite make sense as only the
scala-2.10 profile manages that dependency version up.
Not sure if it's relevant, but I can't see why {{jline.groupid}} is needed now.
It can be inlined. Also I don't see a reason to declare {{jline.version}}
outside of the profiles up top in the parent. Maybe in some strange way that's
being read by a dependency. Maybe worth knocking out as an experiment.
> dev/change-scala-version.sh ends up with incorrect jline dependency for REPL
> ------------------------------------------------------------------------------
>
> Key: SPARK-10037
> URL: https://issues.apache.org/jira/browse/SPARK-10037
> Project: Spark
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4.1
> Environment: ALL
> Reporter: Stephen Boesch
> Priority: Minor
>
> The repl/pom.xml remains untouched after applying
> dev/change-scala-version.sh 2.11
> The line intended to perform the update is
> find "$BASEDIR" -name 'pom.xml' -not -path '*target*' -print \
> -exec bash -c "sed_i
> 's/\(artifactId.*\)_'$FROM_VERSION'/\1_'$TO_VERSION'/g' {}" \;
> The problems:
> repl/pom.xml has usages of the scala version not matching that search pattern:
> <extra.source.dir>scala-2.10/src/main/scala</extra.source.dir>
> <extra.testsource.dir>scala-2.10/src/test/scala</extra.testsource.dir>
> But the REAL problem is that *somehow* the jline dependencies are still
> pulled in. I can not understand why it is (thus I will unfortunately not have
> a PR to provide for this..). After all this same logic is in all the other
> projects. But the fact remains that this code IS invoked.
> The command line i used :
> dev/change-scala-version.sh 2.11
> mvn clean package -DskipTests=true -Pyarn -Phadoop-2.4 -Dhadoop.version=2.6.0
> -Dmaven.javadoc.skip=true -Pscala-2.11
> Here is the error:
> [ERROR] Failed to execute goal on project spark-repl_2.11: Could not resolve
> dependencies for project org.apache.spark:spark-repl_2.11:jar:1.5.0-SNAPSHOT:
> Failure to find org.scala-lang:jline:jar:2.11.7 in
> https://repo1.maven.org/maven2 was cached in the local repository, resolution
> will not be reattempted until the update interval of central has elapsed or
> updates are forced -> [Help 1]
> [ERROR]
> <profile>
> <id>scala-2.10</id>
> <activation>
> <property><name>!scala-2.11</name></property>
> </activation>
> <dependencies>
> <dependency>
> <groupId>${jline.groupid}</groupId>
> <artifactId>jline</artifactId>
> <version>${jline.version}</version>
> </dependency>
> </dependencies>
> </profile>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
