* Build this one first:
https://github.com/apache/maven/tree/maven-3.8.x-resolver-1.7.x
(https://maven.apache.org/resolver/maven-3.8.x.html)
* Follow this guide:
https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html
If you have failures, follow this guide:
*
Hi Tamas,
I've been trying the Redisson approach for the last 7 weeks, but my machine
locks up every second or third build for long periods of time 5-20min.
I'm on Ubuntu running the Redis 6.2.6 snap using the Maven 3.8.3 and 3.8.4
wrapper. I followed these instructions to setup
Edit the file
Thanks Tamás.
Since I use the wrapper, I was thinking there's a case for Maven wrapper
variants. But I guess this is what containers are all about anyway.
Delany
On Thu, 7 Oct 2021 at 11:32, Tamás Cservenák wrote:
> Hi Delany,
>
> from Sisu website: "Sisu is a modular JSR330-based container
Hi Delany,
from Sisu website: "Sisu is a modular JSR330-based container that
supports *classpath
scanning*, *auto-binding*, and *dynamic auto-wiring*. Sisu uses
Google-Guice to perform dependency injection and provide the core JSR330
support, but removes the need to write explicit bindings in
Michael, could you clarify this line pls: "It only works when Sisu DI is
used and not the bundled AetherModule or ServiceLocator (Maven uses Sisu
dependency injection)."
https://maven.apache.org/resolver/maven-resolver-named-locks-redisson/index.html
What should I do about this issue?
Thanks,
Am 2021-10-06 um 21:05 schrieb Francois Marot:
Michael, I do not agree. As a user and maintainer of the build chain in my
company, I think Maven would really benefit from an out of the box
solution. I think any user is susceptible to the bug by launching multiple
Maven instances at the same time
Michael, I do not agree. As a user and maintainer of the build chain in my
company, I think Maven would really benefit from an out of the box
solution. I think any user is susceptible to the bug by launching multiple
Maven instances at the same time on his computer. Bugs then encountered are
Just chiming in on my experience using the redis locks with maven 3.8.x and
resolver 1.6. I've been running it on my Jenkins nodes for about a year now
with great success. Before it, we had corrupted local maven repos (zip file
empty kind of exceptions) a couple of times a week. Then, we
Am 2021-10-04 um 22:13 schrieb Francois Marot:
"Salut" Michael,
thanks for the detailled answer.
Regarding my Jenkins 'hack' you can totally forget about it: it just
ensures no more than one Maven execution uses a given repo at once by
locating the local repositories in a folder reflecting the
"Salut" Michael,
thanks for the detailled answer.
Regarding my Jenkins 'hack' you can totally forget about it: it just
ensures no more than one Maven execution uses a given repo at once by
locating the local repositories in a folder reflecting the executor (which
are kinda Jenkins "threads").
I
Betreff: Re: Local repository accessed by multiple Maven instances - how is it
solved ?
Hi Bernd,
nothing is wrong with advisory file locking, as long as you don't store
local repo on NFS ;)
Will re-add file locking once I get there, as in my opinion it is the most
"lightweight" MP (mul
Tamás,
Redis is so easy to install and get going in 5 minutes that I would
rather see your energy go into areas which need more attention.
M
Am 2021-10-04 um 22:02 schrieb Tamás Cservenák:
Hi Bernd,
nothing is wrong with advisory file locking, as long as you don't store
local repo on NFS
Hi Bernd,
nothing is wrong with advisory file locking, as long as you don't store
local repo on NFS ;)
Will re-add file locking once I get there, as in my opinion it is the most
"lightweight" MP (multi process) solution on a single host.
Redis and Hazelcast are more for "farms", where several
Von: Michael Osipov
Gesendet: Monday, October 4, 2021 9:15:23 PM
An: users@maven.apache.org
Betreff: Re: Local repository accessed by multiple Maven instances - how is it
solved ?
Am 2021-10-04 um 14:31 schrieb Francois Marot:
> Hello all,
>
> I would like clarificatio
Am 2021-10-04 um 14:31 schrieb Francois Marot:
Hello all,
I would like clarifications on MNG-2802[*] that seems to be solved. If I
understand correctly it solves the problem where multiple simultaneous
Maven executions shared the same local repository.
I have been keeping for years a bit of
Yes, these are good news!
Am 04.10.21 um 15:10 schrieb Thomas Broyer:
From JIRA links, this is apparently fixed by
https://issues.apache.org/jira/browse/MRESOLVER-131, which means you need
to deploy a Redis server.
There apparently also is an Hazelcast-based version:
Wooohaa, thanks Thomas.
It's a whole new world being revealed to me: I wasn't aware of the huge
work happening on artifact resolvers.
At the same time, it seems not to be available out of the box (needs a
Redis server) so I'll keep my Jenkinsfile hacks for now and will wait
for proper
>From JIRA links, this is apparently fixed by
https://issues.apache.org/jira/browse/MRESOLVER-131, which means you need
to deploy a Redis server.
There apparently also is an Hazelcast-based version:
https://maven.apache.org/resolver/maven-resolver-named-locks/index.html
On Mon, Oct 4, 2021 at
Hello all,
I would like clarifications on MNG-2802[*] that seems to be solved. If I
understand correctly it solves the problem where multiple simultaneous
Maven executions shared the same local repository.
I have been keeping for years a bit of code in my Jenkinsfiles ensuring the
local repos
19 matches
Mail list logo
