IntelliJ difficulties with guava classes

[Michael Burton]

Is there a recommended way to build guice from within IntelliJ?  It works fine using maven, but when I try to edit or build code from IntellIJ 13 I see a number of errors due to unresolved dependencies in things like the Guava library.  I assume this is because of the way the build is using jarjar to remap com.google.common.* to com.google.inject.internal.guava.*.

Is there a way to get the IntelliJ editor to recognize the guava classes?  

Mike

[Sam Berlin]

In Eclipse, I just put in the source & jars.  Not sure what IntelliJ would be doing ... maybe it's trying to build a layout off the POMs and is confused since the current POM setup shades the dependencies?

 sam

--
You received this message because you are subscribed to the Google Groups "google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-guice...@googlegroups.com.
To post to this group, send email to google...@googlegroups.com.
Visit this group at http://groups.google.com/group/google-guice.
For more options, visit https://groups.google.com/groups/opt_out.

[David Hoffer]

I'd summit this issue to JetBrains....see what they say.

-Dave

[Brian Pontarelli]

Did you try “Invalidate Caches”?

-- Brian

[Michael Burton]

I tried re-importing from maven and invalidating the caches.  Neither worked, but I was able to fix it by going into the Modules configuration and removing the broken "guava (1)",  "guava (2)" and "guava (4)" modules.  Not sure how they got in there, but everything works now.

Thanks for the assistance!

--
You received this message because you are subscribed to a topic in the Google Groups "google-guice" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-guice/e6qgIW4UWJg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-guice...@googlegroups.com.

[Mark Derricutt]

I've noticed this a few times with IntelliJ lately, when you reimport
the project with new versions, it doesn't seem to remove the old version
references, with eventually leads you to red-errors everywhere ( really
hurts on our project with 30 or so artefacts all coming from regularly
released version ranges!!! ).