This message was deleted.

the

artifact {}

block doesn’t have a

files()

function

dependencies {
  implementation("com.twitter:twitter-api-java-sdk:2.0.3") {
    artifact {
      this.files() // ERROR: Unresolved reference: files
    }
  }
}

IntelliJ suggested me towards that solution and it didn't explode. 🤔 (I know IntelliJ has never been reliable on gradle syntax)

it won’t explode, but it also won’t do anything :).

files()

calls Project.files(), which will create a new file collection, which is allowed, but then nothing happens

Haha voiding the result. Perfect. 😛

if what you have here https://gradle-community.slack.com/archives/CAHSN3LDN/p1689522787197249 works, then that sounds good. I think there might be a way to do it properly with some sort of custom dependency resolution rule https://docs.gradle.org/current/userguide/resolution_rules.html, but those are phenomenally complicated and difficult. Or with an exclusion / local file-based repository https://stackoverflow.com/questions/19701053/how-do-i-replace-a-gradle-module-dependency-with-a-jar, but that seems hacky.

The solution I found works. But it lost its

javadoc

and

sources

reference. If there is a way to provide them into the

implementation

thing, that would be great!

how are you building this custom artifact?

Opened up that project locally and ran maven package, got four jars;

main

,

javadoc

,

sources

and

test

. Copied them over to this project. Didn't want to publish.

if you want to keep the sources (Javadoc shouldn’t be necessary if you have the sources, right?), then maybe you could add it as an included build? https://github.com/melix/includegit-gradle-plugin

Yeah, I was thinking of a subproject thing. But mixing wont work

you could publish it to MavenLocal?

Sure, I guess I could. Would work fine on my dev environment, but will be problem later with building docker images in ci or whatever

this is the project? https://github.com/twitterdev/twitter-api-java-sdk

yeah

hmmmm well, there are a few options. One would be to fork it and convert it to a Gradle project. It doesn’t look that complicated - just check it out, cd into project dir, and run

gradle init

to run the auto conversion

And then I could include that fork as a dependency via that plugin you linked?

yes that’s right

It generated with

api

instead of

implementation

, what's the difference? Does it matter?

or probably the easiest, but most manual, is to just manually build & publish to Maven Local, and then copy the files - while keeping the directory structure - into your project So if Maven Local looks like this:

.
└── m2/
    └── repository/
        └── com/
            └── blah/
                ├── whatever/
                │   ├── whatever.jar
                │   └── whatever-sources.jar
                └── maven.xml

Then you’d add in your project:

.
└── myProject/
    └── maven-dir/
        └── com/
            └── blah/
                ├── whatever/
                │   ├── whatever.jar
                │   └── whatever-sources.jar
                └── maven.xml

Then add a local Maven directory for that file:

repositories {
  maven(file("./maven-dir/"))
}

ah it provides it upwards

nice!

It's a bit hacky, and I know it shouldn't be done. But whatever 😂

if it’s stupid and it works it’s not stupid 👍

haha true

you’re welcome :)

Regarding your original question, did you try

implementation("com.twitter:twitter-api-java-sdk:2.0.3") {
    artifact {
        url = uri("libs/twitter-api-java-sdk/twitter-api-java-sdk-2.0.3-jakarta10.jar").toString()
    }
}

(or something like that)