Guillaume Nodet

Results 255 comments of Guillaume Nodet

More information would be helpful. Do you know which files are locked ? Any way to reproduce the problem ?

Not sure why tests aren't running. I'll close this one and recreate a new PR.

> Not sure why tests aren't running. I'll close this one and recreate a new PR. Ah, closing and reopening did the trick.

> We have TLS-based solutions in past releases and we had to revert. What makes this one different? It's not a new TLS, it's a move of the existing TLS...

I can write one for MNG-7474. MNG-7401 is an internal behavior and would require a junit test rather than an IT imho.

> > I can write one for [MNG-7474](https://issues.apache.org/jira/browse/MNG-7474). [MNG-7401](https://issues.apache.org/jira/browse/MNG-7401) is an internal behavior and would require a junit test rather than an IT imho. > > I guess so that...

It seems to work for me: ``` ➜ ~ docker run --rm -it jenkins/inbound-agent:latest-alpine-jdk11 bash bash-5.1$ wget https://github.com/apache/maven-mvnd/releases/download/0.7.1/mvnd-0.7.1-linux-amd64.zip Connecting to github.com (140.82.121.3:443) Connecting to objects.githubusercontent.com (185.199.108.133:443) saving to 'mvnd-0.7.1-linux-amd64.zip' mvnd-0.7.1-linux-amd...

Try modifying the `[MVND_HOME]/conf/mvnd.properties` to change the `mvnd.minHeapSize` and `mvnd.maxHeapSize` properties to proper values. This has been for the next release already (see https://github.com/apache/maven-mvnd/issues/560).

@ppalaga you've tested it with the recent changes around the maven caches ?

@ppalaga I can't reproduce with quarkus master and mvnd 0.3.0. The changes seem to be correctly picked up by the daemon when running the test after rebuilding the deployment module.