fix(utiles): evitar dependencia de junit-bom y fijar versión de JUnit para tests#7
Merged
hamfree merged 1 commit into1.3-SNAPSHOTfrom Feb 22, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
org.junit:junit-bomy la propiedadjunit.versiondejaban ajunit-jupiter-enginesin una versión explícita cuando el BOM no se resolvía, provocando fallos de resolución de modelo en entornos con acceso restringido a Maven Central.Description
junit.versionde laspropertiesenutiles/pom.xml.dependencyManagementque importabaorg.junit:junit-bomdesde el BOM.5.11.0a la dependenciaorg.junit.jupiter:junit-jupiter-engineen las dependencias de test.utiles/pom.xmlpara que la resolución de dependencias de tests no dependa del BOM externo.Testing
mvn test -qenutiles/antes del cambio y la ejecución falló con un error de resolución del BOM (org.junit:junit-bom) y una dependencia sin versión, reproduciendo el problema original.mvn test -qy ya no aparece el fallo de BOM/version de JUnit; el build ahora falla por resolución de plugins (por ejemplomaven-enforcer-plugin) debido a respuestas403 Forbiddendesde Maven Central en este entorno, por lo que los tests unitarios no pudieron completarse aquí.Codex Task