You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The build consists of a custom build script that does some setup, builds Maven dependencies that are not found in any other repositories and adds those to the local maven repository, and then builds the project itself (using Gradle) and publishes its results to the local maven repository as well.
The build runs fine locally and on Github Actions, and appears to also run fine on Jitpack according to the log.
Jitpack also mentions that it finds the resulting artifacts after the build.
Found artifact: com.nisovin.shopkeepers:ShopkeepersAPI:2.19.1-SNAPSHOT
Found artifact: com.nisovin.shopkeepers:ShopkeepersMain:2.19.1-SNAPSHOT
But at the very end, it does not list those jar files in the
Edit: If I remove those other dependency artifacts, it actually complaints that it cannot find any build results, even though the results are in the local maven repository after the build, as confirmed by checking for the files via some bash script.
It seems that whenever I incldue building these other dependencies, either during before_install, or as setup script during install, or by triggering the build script from within the Gradle build itself, Jitpack no longer finds/checks for the relevant project artifacts.
If I omit the building of those other dependencies, and then only build the 'api' module, with some minor changes to its dependencies so that it does not depend on those other locally built dependencies, Jitpack finds the artifact correctly.
Does the project build on your machine with the same commands (e.g. ./gradlew install) ? Yes
What error are you seeing? None
Thank you!
The text was updated successfully, but these errors were encountered:
blablubbabc
changed the title
Jar file is empty (only contains jitpack generated pom)
No build artifacts found when mixing Maven and Gradle build
May 5, 2024
Hi!
The build consists of a custom build script that does some setup, builds Maven dependencies that are not found in any other repositories and adds those to the local maven repository, and then builds the project itself (using Gradle) and publishes its results to the local maven repository as well.
The build runs fine locally and on Github Actions, and appears to also run fine on Jitpack according to the log.
Jitpack also mentions that it finds the resulting artifacts after the build.
But at the very end, it does not list those jar files in the
It only find the other built dependencies there.
And when trying to depend on the project, the downloaded artifact (https://jitpack.io/com/github/Shopkeepers/Shopkeepers/master-v2.19.0-g7eaea23-11/) is mostly empty: It only contains some Jitpack generated pom file.
Edit: If I remove those other dependency artifacts, it actually complaints that it cannot find any build results, even though the results are in the local maven repository after the build, as confirmed by checking for the files via some bash script.
It seems that whenever I incldue building these other dependencies, either during before_install, or as setup script during install, or by triggering the build script from within the Gradle build itself, Jitpack no longer finds/checks for the relevant project artifacts.
If I omit the building of those other dependencies, and then only build the 'api' module, with some minor changes to its dependencies so that it does not depend on those other locally built dependencies, Jitpack finds the artifact correctly.
Please provide:
Build log: https://jitpack.io/com/github/Shopkeepers/Shopkeepers/master-v2.19.0-g7eaea23-11/build.log
Does the project build on your machine with the same commands (e.g. ./gradlew install) ? Yes
What error are you seeing? None
Thank you!
The text was updated successfully, but these errors were encountered: