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
Both test framework and test suite GH Actions CI uses .github/mvn-settings.xml.
But the tests that run mvn command do not reflect that settings. These executions rely on settings file in the default location.
CC @mjurc@michalvavrik wdyt about support for custom settings file for the tests based maven invocation?
The same could apply for custom maven.repo.local. But on the other hand, this would be probably just Maven specific.
The text was updated successfully, but these errors were encountered:
But the tests that run mvn command do not reflect that settings. These executions rely on settings file in the default location.
It would allow us to stop copying settings to ~/.m2 as we do in Jenkins jobs, right? +1
The same could apply for custom maven.repo.local. But on the other hand, this would be probably just Maven specific.
TBH I thought system properties are already propagated, so I'd expect maven.repo.local to work already. Probably wrong now that I read your description.
Both test framework and test suite GH Actions CI uses
.github/mvn-settings.xml
.But the tests that run mvn command do not reflect that settings. These executions rely on settings file in the default location.
CC @mjurc @michalvavrik wdyt about support for custom settings file for the tests based maven invocation?
The same could apply for custom
maven.repo.local
. But on the other hand, this would be probably just Maven specific.The text was updated successfully, but these errors were encountered: