Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

954
Vistas
ERROR: No build artifacts found - Maven Jitpack

Note: Before you mark this as duplicate please check all information as after 4 hours of search I couldn't find any close cases. All results were about Android Library or Gradle which is not correct on this case.

Links:

Build Log: https://jitpack.io/xyz/agmdev/AGMCore/3.3.1/build.log

Github Source: https://github.com/Ashenguard/AGMCore

Error:

Exit code: 0
Timed out after 20 min

ERROR: No build artifacts found
Project: Maven - Spigot
Version: 3.3.1

Today after finishing the coding, compiling, testing (All of them were successful on my PC) I decided it's time to upload it on Github and create the 3.3.1 release on jitpack.io so I or any other developer can use it in further projects as dependency.

Everything was ok until I started the new project depending on the new code I just uploaded. But I faced the dependency not found on my IDE (Intelij) and I thought it is a connection issue or something similar, But after troubleshooting, I got to the Build being failure on jitpack.io.

Before you ask, I did test mvn install and it worked fine without any issue on my PC, but for some reason that I'm not aware of, jitpack fails... What confused me more only thing that has been changed on pom.xml since the last successful build, is the version number

Possible issues that were not the issue in this case. (I'll update the list)

  • Packaging not being jar which was, Same as previous versions.
  • useIncrementalCompilation was not the issue as well.
over 4 years ago · Santiago Trujillo
1 Respuestas
Responde la pregunta

0

This error can happen in multiple scenarios.

Scenario 1:

  • If the build fails
  • If there are no pom.xml or .pom files in build directory
  • If artifacts are not copied to $HOME/.m2/...

Scenario 2:

  • You can fix it by looking at https://github.com/jitpack/maven-modular

Scenario 3:

  • Try this jitpack example

Note: You can only solve it by yourself making sure you have double check your poms.

--- Updated --

Workaround:

Try to add JitPack repository and dependency in your pom.xml file:

JitPack repository:

<repositories>
    <repository>
        <id>jitpack.io</id>
        <url>https://jitpack.io</url>
    </repository>
</repositories>

JitPack dependency:

<dependency>
    <groupId>com.github.YourProjectName</groupId>
    <artifactId>ID</artifactId>
    <version>Tag</version>
</dependency>

Maybe it can fix the issue as you said it only occurs on JitPack.

over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda