Jump to content

[SOLVED] Error com.google.common.collect.Multimap cannot be resolved


Daeruin

Recommended Posts

I just tried to make a new tool in my mod, and I'm getting an error:

 

The type com.google.common.collect.Multimap cannot be resolved. It is indirectly referenced from required .class files

 

I've been searching online for a couple hours and haven't figured out how to fix this. I finally deleted Forge and Eclipse and reinstalled from scratch, and I'm still getting this error. Any idea what's up?

Link to comment
Share on other sites

That is part of the guava library  (guava-17.0.jar) which Forge normally installs and adds to the project automatically when building the workspace.  Forge uses quite a few parts of it.

 

You could try looking to make sure that the guava-17.0.jar is in the list of libraries - might help troubleshoot - but unfortunately I don't have any other ideas (I use IntelliJ instead of Eclipse)

 

-TGG

Link to comment
Share on other sites

That is part of the guava library  (guava-17.0.jar) which Forge normally installs and adds to the project automatically when building the workspace.  Forge uses quite a few parts of it.

 

You could try looking to make sure that the guava-17.0.jar is in the list of libraries - might help troubleshoot - but unfortunately I don't have any other ideas (I use IntelliJ instead of Eclipse)

 

-TGG

That gave me the clue I needed. How did you know that com.google.common.collect.Multimap was part of the guava library? I checked my build path, and sure enough that library wasn't listed. After a bit of fiddling, I finally found where the library was located in my system and was able to add it as an external jar. Is there a better way of doing it?

 

It sounds like the library should have been in my build path already if Forge was set up correctly. It makes me think there are probably other missing libraries, but I'm not sure what it's supposed to look like.

Link to comment
Share on other sites

That gave me the clue I needed. How did you know that com.google.common.collect.Multimap was part of the guava library?

 

Pretty much everything (actually everything?) in the com.google.common package is part of the Guava library.

Apparently I'm a complete and utter jerk and come to this forum just like to make fun of people, be confrontational, and make your personal life miserable.  If you think this is the case, JUST REPORT ME.  Otherwise you're just going to get reported when you reply to my posts and point it out, because odds are, I was trying to be nice.

 

Exception: If you do not understand Java, I WILL NOT HELP YOU and your thread will get locked.

 

DO NOT PM ME WITH PROBLEMS. No help will be given.

Link to comment
Share on other sites

That gave me the clue I needed. How did you know that com.google.common.collect.Multimap was part of the guava library? I checked my build path, and sure enough that library wasn't listed.

Keen.  I knew about guava because I just happened to look up MultiMap a month or so ago and stumbled on the guava library :), there is a stack of useful stuff in there

https://github.com/google/guava/wiki

Well worth a couple of hours' browsing if you're serious about Java coding I reckon.

 

 

 

After a bit of fiddling, I finally found where the library was located in my system and was able to add it as an external jar. Is there a better way of doing it?

 

It sounds like the library should have been in my build path already if Forge was set up correctly. It makes me think there are probably other missing libraries, but I'm not sure what it's supposed to look like.

I don't know of a better way than that - and I've never had to do it manually myself.

 

If there are any other missing libraries, your compiler will probably tell you when you try to compile so just worry about that when it happens I reckon.  There are about 60 of them....

 

-TGG

 

Link to comment
Share on other sites

  • 4 weeks later...

I'm replying to my own month-old thread because I had the same problem again and had to look it up so I could remember the solution. Unfortunately, I didn't post the details. So here they are.

 

In Eclipse:

 

1. Right click on the project in the Package Explorer.

2. Choose Build Path > Configure Build Path.

3. In the Libraries tab, choose Add External JARs.

4. Navigate to the physical location of the missing library. In my case, it was Users/~/.gradle/caches/modules-2/files-2.1/ and then into the specific package needed.

 

I still don't understand why this is needed, because I can see the forge project in my Package Explorer, and if I go into the Referenced Libraries, I can see the ones that are missing from my build path. I must have set up something wrong, but I don't know what. Anyhow, hopefully this helps someone else in the future.

 

Edit: Clarified instructions.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.