-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to use caliko in a Gradle project? #18
Comments
I didn't end up uploading Caliko to the maven repos in the end because it was a lot of hoop-jumping that I wasn't really interested in doing. The easiest way to use the libraries is through the jar files provided in each Caliko release. There's a write-up about how to do this (using Eclipse as the target IDE) in the user documentation. Cheers! |
I'm trying the same for Maven, no luck yet.
|
I ended up installing it locally (but the jit path would ne nice for the future)
<dependency>
<groupId>au.edu.federation.caliko</groupId>
<artifactId>caliko</artifactId>
<version>1.3.8</version>
</dependency> |
Unfortunately I'm pretty rubbish with maven - with regard to the jit path, do you mean I should add something like this to the README.md: To obtain the library in maven via JitPack.io, please add the JitPack repository to your build file: <repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories> And then add the Caliko dependency as shown below: <dependency>
<groupId>com.github.FedUni</groupId>
<artifactId>caliko</artifactId>
<version>v1.3.8</version>
</dependency> Is that what you mean? I'd never even heard of jitpack before 5 minutes ago, lol. |
That is exactly what I meant! Normally it is a very easy way to get a build
of a project that has commits and or releases that aren't up in maven
central. (I too am bad at maven)
I did those steps,
but it isn't working for some reason.
The compile logs in jitpack said it borked.
…On Sat, Aug 8, 2020, 2:47 AM Al Lansley ***@***.***> wrote:
Unfortunately I'm pretty rubbish with maven - with regard to the jit path,
do you mean I should add something like this to the README.md:
To obtain the library in maven via JitPack.io, please add the JitPack
repository to your build file:
<repositories>
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
</repositories>
And then add the Caliko dependency as shown below:
<dependency>
<groupId>com.github.FedUni</groupId>
<artifactId>caliko</artifactId>
<version>v1.3.8</version>
</dependency>
Is that what you mean? I'd never even heard of jitpack before 5 minutes
ago, lol.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#18 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAU25TNT2Y4U4Q6FH37XODR7UNK3ANCNFSM4MROTZ4Q>
.
|
Haha, I know less than you about this stuff, mate. If you want to fix it then clone the repo, make your changes and submit a pull request with a detailed commit log - I'll accept anything that's sane and useful. Emphasis on sane and useful ;-) |
Hello,
I'm probably just bad at Gradle but doing
dependencies{ implementation("au.edu.federation.caliko:caliko:1.3.6") implementation("au.edu.feduni.caliko.visualisation:caliko-visualisation:1.3.6")
gives me
`A problem occurred evaluating root project 'BaseElbow'.
What should I use instead?
The text was updated successfully, but these errors were encountered: