[
https://issues.apache.org/jira/browse/MNG-7539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17606295#comment-17606295
]
Karl Heinz Marbaise commented on MNG-7539:
------------------------------------------
If your update of the SNAPSHOT's is always it means you have either configured
that in your {{settings.xml}} ([Update
Policy|https://maven.apache.org/settings.html#repositories]) or you are using
{{-U}} during your build..The update intervall can already being defined via
{{settings.xml}} (see updatePolicy)...
Furthermore:
{quote}Maven Repository (a local Nexus instance), and artifact resolution could
slow down the build 2x-3x.{quote}
That sounds like if your repository manager has not enough power to handle such
simple load... Also the question is: Does the build of your multi module build
(30-40 modules) takes really 10-15 minutes?
>From my point of view you could solve the whole issue by using releases of the
>needed components in your projects... and test updates (new release versions)
>on a separate branch... and hopefully having appropriate tests to verify ...
>... The other question might be if your project heavily relies on other
>componenets (high coupling) it might be an option to reconsider to integrate
>those components in your multi modules builds...
> Validate/Download SNAPSHOT dependencies once
> --------------------------------------------
>
> Key: MNG-7539
> URL: https://issues.apache.org/jira/browse/MNG-7539
> Project: Maven
> Issue Type: Improvement
> Components: Dependencies
> Reporter: Adrian Tarau
> Priority: Critical
>
> Building an unreleased multi-module project (30-40 modules) that depends on
> various other unreleased modules puts significant pressure on the Maven
> Repository (a local Nexus instance), and artifact resolution could slow down
> the build 2x-3x.
> I do acknowledge that it is the job of the repository to cache and serve
> those responses fast, and for some reason, sometimes it slows down without an
> apparent reason.
> However, the whole build process will be faster if Maven validates a SNAPSHOT
> once for multi-module (when the dependency is reached the first time) and
> then use that version. Even if Maven Repository is relative fast, there is
> still network traffic done. Outside the fact that it should not be done, it
> might also introduce flaky behaviors:
> * one module downloads a version of artifact A, works with it, and
> everything is fine
> * 10 minutes later, another module needs artifact A and gets a newer
> version, which has some issues, and various (test) failures will be raised
> For consistency, on a multi-module build, all modules should _see_ the same
> version of a SNAPSHOT artifact. It will be faster, and it will be consistent
> (which is very important).
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
