slawekjaranowski commented on PR #307:
URL:
https://github.com/apache/maven-integration-testing/pull/307#issuecomment-1747724177
> > Master build is still suffer from it ... do we have any other idea - how
to fix After release alpha-8 we will can remove access to remote repo and move
needed artifacts to bootstrap.
>
> I still think we should run the integration tests on a locally build
distribution, else there's no way we can test something depending on new code
in maven. So for the time being, I would either disable the test until alpha-8
is released or build Maven snapshot locally (or disable Jenkins jobs which are
the only one failing).
We run test on current build distribution:
```
Running integration tests for Maven 4.0.0-alpha-8-SNAPSHOT
using Maven executable:
/home/jenkins/jenkins-home/workspace/Maven_maven-box_maven_MNG-7898/test/core-it-suite/target/apache-maven/bin/mvn
with verifier.forkMode: auto
```
We only don't have populated local repo used by test by Maven build
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
