So I opened it as a maven project (I opened it using the top-level pom.xml
file), but rebuilding the project ends up in all sorts of errors about
unresolved dependencies.
Thanks,
Ron
On Wednesday, August 6, 2014 11:15 PM, Sean Owen wrote:
(Don't use gen-idea, just open it directly as a Ma
Ron,
I was able to build core in Eclipse following these steps:
https://cwiki.apache.org/confluence/display/SPARK/Contributing+to+Spark#ContributingtoSpark-Eclipse
I was working only on core, so I know that works in Eclipse Juno.
I haven't tried yarn or other Eclipse releases.
Are you able to bu
(Don't use gen-idea, just open it directly as a Maven project in IntelliJ.)
On Thu, Aug 7, 2014 at 4:53 AM, Ron Gonzalez
wrote:
> So I downloaded community edition of IntelliJ, and ran sbt/sbt gen-idea.
> I then imported the pom.xml file.
> I'm still getting all sorts of errors from IntelliJ abou
Thanks, will give that a try.
Sent from my iPad
> On Aug 6, 2014, at 9:26 PM, DB Tsai wrote:
>
> After sbt gen-idea , you can open the intellji project directly without going
> through pom.xml
>
> If u want to compile inside intellji, you have to remove one of the messo
> jar. This is an ope
After sbt gen-idea , you can open the intellji project directly without
going through pom.xml
If u want to compile inside intellji, you have to remove one of the messo
jar. This is an open issue, and u can find the detail in JIRA.
Sent from my Google Nexus 5
On Aug 6, 2014 8:54 PM, "Ron Gonzalez"
So I downloaded community edition of IntelliJ, and ran sbt/sbt gen-idea.
I then imported the pom.xml file.
I'm still getting all sorts of errors from IntelliJ about unresolved
dependencies.
Any suggestions?
Thanks,
Ron
On Wednesday, August 6, 2014 12:29 PM, Ron Gonzalez
wrote:
Hi,
I'm t
Ok I'll give it a little more time, and if I can't get it going, I'll switch. I
am indeed a little disappointed in the Scala IDE plugin for Eclipse so I think
switching to IntelliJ might be my best bet.
Thanks,
Ron
Sent from my iPad
> On Aug 6, 2014, at 1:43 PM, Sean Owen wrote:
>
> I think
I think your best bet by far is to consume the Maven build as-is from
within Eclipse. I wouldn't try to export a project config from the
build as there is plenty to get lost in translation.
Certainly this works well with IntelliJ, and by the by, if you have a
choice, I would strongly recommend Int
