Jump to content

Recommended Posts

Posted

For some reason, my dependency doesn't seem to be working. I used the XStream library (version 1.4.7) in my mod. So, in my build.grade I included the following:

    compile 'org.jsoup:jsoup:1.7.2'
    compile 'com.thoughtworks.xstream:xstream:1.4.7'

 

As you can see, I also have a jsoup dependency, which is working fine and dandy. You can view the XStream maven info here. When I run gradlew build, there is no error thrown (in fact, I could see it downloading everything). But, when I give someone else the file, they receive this error upon running:

 

 

  Reveal hidden contents

 

 

Any ideas how I could fix this? :(

Posted
  On 12/12/2014 at 10:52 PM, diesieben07 said:

JSoup will not work either. Gradle does not package dependencies with your mod.

 

But nobody has had problems with JSoup. Could it be because JSoup has no other dependencies but XStream does?

Posted
  On 12/12/2014 at 11:15 PM, diesieben07 said:

It just crashes with XStream because you use that first in your mod ....

 

No, JSoup works fine, please trust me. I have used it for some time, and created versions of my mod where JSoup was used successfully.

Posted
  On 12/13/2014 at 12:03 AM, diesieben07 said:

That is impossible unless your users install it separately or it is on the classpath for some other reason.

Pleas trust me: Gradle does not package libraries automatically.

 

Ugh, I'll take your word for it, though I can't imagine people have JSoup installed...

Why does gradlew build not throw any errors? Because I have the requirements on my system?

 

Also, you mentioned something in another topic about all jars in /build/libs being marked as dependencies. Can that help me?

Posted
  On 12/13/2014 at 1:55 AM, diesieben07 said:

No. This is on the build side. All dependencies are resolved in your development environment. But when users install your mod there is no gradle or anything like that to do that. So you have to either ship the dependencies yourself or get users to install them.

 

Right. So you suggest using the Gradle Shadow Plugin to ship the dependency?

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.