Found the karaf issue, went to 3.9.10 and https://gist.github.com/cstamas/4b80c164506ec4f0c4bf2f6c4acaf436
did several builds and "releases" (of course, at end I failed w/o auth), still nada. T On Fri, Jan 23, 2026 at 6:55 PM Tamás Cservenák <[email protected]> wrote: > > For full details: > [cstamas@angeleyes oldalbum (master)]$ mvn -v > Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1) > Maven home: /home/cstamas/.sdkman/candidates/maven/current > Java version: 21.0.9, vendor: Eclipse Adoptium, runtime: > /home/cstamas/.sdkman/candidates/java/21.0.9-tem > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "6.18.5-200.fc43.x86_64", arch: "amd64", > family: "unix" > [cstamas@angeleyes oldalbum (master)]$ > > T > > On Fri, Jan 23, 2026 at 6:53 PM Tamás Cservenák <[email protected]> wrote: > > > > Howdy, > > > > I cannot reproduce, with setup like yours (at mail beginning) I get this: > > https://gist.github.com/cstamas/c7dcbda6d51f9d37d72c2d8517340425 > > > > Thanks > > T > > > > On Fri, Jan 23, 2026 at 4:57 PM Steinar Bang <[email protected]> wrote: > > > > > > debian 13.3 "trixie", amd64, Java 21.0.4, maven 3.9.10 > > > > > > If anyone have ideas about this I will be grateful. > > > > > > I am thinking either a timing issue or a dependency issue, but I may be > > > barking up the wrong tree...? > > > > > > Here is the problem: > > > > > > For project https://github.com/steinarb/oldalbum then right now (and for > > > the last three releases) has failed on > > > mvn release:prepare > > > > > > but if I add an -X to get more debug output, then "release:prepare" runs > > > without error: > > > mvn -X release:prepare > > > > > > The error happens in the maven build of the release version (i.e. the > > > version without SNAPSHOT). > > > > > > Builds on SNAPSHOT versions with > > > mvn clean install > > > runs without issue. > > > > > > Builds on the release version (after release:prepare has failed) with > > > mvn clean install > > > > > > What the failure actually is varies (it is not reproducible from run to > > > run), but most of the time it seems to be related to the test class not > > > being able to find production code, sometimes, like here, production > > > code in the same maven module > > > > > > https://gist.github.com/steinarb/3a3c68c08ed1820622314fde1c3c5421#file-build_log-L391 > > > > > > One thing that doesn't vary between the different failures is that it is > > > tests in one of the maven modules that fail. > > > > > > I do: > > > mvn release:rollback > > > rm -rf ~/.m2/repository/no/priv/bang/oldalbum/ > > > between test runs. > > > > > > Tests of liquibase code often fails and liquibase uses SPI in the setup, > > > if > > > that helps (the reason I am thinking about SPI is because "-X" would > > > maybe change timing and give stuff a change to start and dependency > > > inject...?). > > > > > > I also use TwelveMonkeys image processing code in this project and > > > TwelveMonkeys also use SPI (since TwelveMonkeys implements ImageIO). > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
