astefanutti commented on issue #3831: URL: https://github.com/apache/camel-k/issues/3831#issuecomment-1326141685
> > > It seems to be a good starting point but please mind that accessing the local maven repo concurrently was an issue in the past with maven (https://issues.apache.org/jira/browse/MNG-2802) > > > > > > Wasn't aware of that. Definitely I'll keep that in mind. It seems it was fixed starting from Maven 3.8.2, but it is not very clear from the comments I can read on that issue. If we follow this design, we can always find a way to have builds sequentially, although we loose the ability to scale (or let the user choose a parallel building without shared volume for Maven cache). > > Note that scaling is also potentially limited by the image reuse strategy we have in camel-k, i.e. see #592 Mind that we should review what concurrency safety guarantees MNG-2802 provide, here we are talking about accessing the same local Maven repository via different Maven instances, executed on different machines. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
