How to include dependencies during maven-publish

Help/Discuss
1

I have build.gradle file

plugins {
    id "java-library"
    id "maven-publish"
    id "com.jfrog.artifactory" version "4.32.0"
}
// maven-publish plugin
tasks.register('apiJar', Jar) {
    from sourceSets.main.output
    from sourceSets.test.output
    exclude(....)
}
tasks.register('sourceJar', Jar) {
    from sourceSets.main.allJava
    from sourceSets.test.allJava
    archiveClassifier = "sources"
}
publishing {
    publications {
        maven(MavenPublication) {
            artifact apiJar
            artifact sourceJar
        }
    }
}
// com.jfrog.artifactory plugin
artifactory {
    contextUrl = "${artifactory_contextUrl}"
    publish {
        repository {
            repoKey = '${artifactory_key}'
            username = "${artifactory_user}"
            password = "${artifactory_password}"
            maven = true
        }
        defaults {
            publications('maven')
            publishArtifacts = true
            publishPom = true
        }
    }
}

How to add dependencies into pom.xml when I publish artifact?

previously I’ve used this variant

// maven-publish plugin
tasks.register('sourceJar', Jar) {
    from sourceSets.main.allJava
    from sourceSets.test.allJava
    archiveClassifier = "sources"
}
tasks.register('testJar', Jar) {
    dependsOn testClasses
    archiveClassifier = "test"
    from sourceSets.test.output
    exclude(....)
}
publishing {
    publications {
        maven(MavenPublication) {
            from components.java

            artifact sourceJar
            artifact testJar
        }
    }
}

but now I need make one artifact that will include source from “src/main” and “src/test” and add some files from “src/main” to exclusion

2

If you really want to ship those classes together, you should probably just move them from src/test/java to src/main/java.
But most probably it would be a better idea to just use the java-test-fixtures plugin as the test fixtures are then by default also published automatically and a downstream project can depend on specifically the test fixtures in their tests when necessary.

Btw. you should neither define artifact... directly in a publication, but better add it to the java component, nor do you need to manually set up a sourcesJar task, you can simply do java { withSourcesJar() } which will create a sources jar task and also publish it properly.

3

The problem is more about the need to exclude some classes from ‘src/main’.
I find out only one solution for this problem

tasks.register('apiJar', Jar) {
    from sourceSets.main.output
    exclude("path/to/class")
}

I don’t know how to specify that I also need to generate the pom file with dependencies in that case
Previously this work has been covered by this part

        maven(MavenPublication) {
            from components.java
           ...

but now if I use

        maven(MavenPublication) {
            from components.java
            artifact apiJar
            ...

I get an error: “Invalid publication ‘maven’: multiple artifacts with the identical extension and classifier (‘jar’, ‘null’).”

4

Yeah, well, what the error tells you.
You try to publish two jars with the same coordinates, as your apiJar has no classifier, so has the same coordinates as the original jar.

Besides that - as said before - you should not use artifact ... in the plublication, but if you want to add an artifact there, add it to the java component instead.

How to properly solve your issue is hard to say, as it is still unclear what you want to achieve. You could for example define a classifier for the apiJar task if you indeed want to publish it additionally. Or you could for example do the exclude on the standard jar task if not.