Closed maybeec closed 1 year ago
For reference, the github actions run: https://github.com/devonfw/cobigen/actions/runs/4005050174/jobs/6875112523#step:7:8933
@maybeec thanks for reporting. Indeed stupid that default instance was initialized eagerly causing the error. Fixed.
Mh no, I didn't put any special configuration in place to hinder you editing the pr... Strange
For the record 0.9.2 has been released some time ago. https://repo1.maven.org/maven2/io/github/m-m-m/mmm-code-java-impl/0.9.2/ If you wonder why you cannot see the 0.9.2 in the artifact folders like here: https://repo1.maven.org/maven2/io/github/m-m-m/mmm-code-java-impl This is a OSSRH issue (https://issues.sonatype.org/browse/OSSRH-92124)
Steps to reproduce
Actual behavior
We have such behavior in CobiGen on the CI/CD resulting in the following stack trace. We don't use the default maven repository as of github/cache usage across OS. - different story :) It seems, that
MavenBridgeImpl
is actually requiring the folder to exist, which will end in anIllegalStateException
exception. This is even more stupid as it also occurs in case you are instantiating the MavenBridgeImpl properly with a valid repository path.Expected behavior
Affected version