You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2020/10/11 18:23:00 UTC

[jira] [Closed] (MNG-6274) Snapshot timestamps of modules in multimodule build are not aligned

     [ https://issues.apache.org/jira/browse/MNG-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNG-6274.
-------------------------------
    Resolution: Not A Bug

Closing this with the following justification: The current approach is designed to handle each remote snapshot metadata decoupled/separately. Since this is a design choice, I see no appearent bug here. What you are requesting is a design change, hence an improvement request for the sake of consistency.

> Snapshot timestamps of modules in multimodule build are not aligned
> -------------------------------------------------------------------
>
>                 Key: MNG-6274
>                 URL: https://issues.apache.org/jira/browse/MNG-6274
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories, core
>    Affects Versions: 3.5.0
>            Reporter: James Nord
>            Assignee: Michael Osipov
>            Priority: Major
>
> If you have a multi-module build with SNAPSHOT versions and deploy it to your repository all of the modules have different time-stamps.
> This is a pain when you want to refer to many of these snapshots in a different project.
> Rather than being able to update a single property to reference the newly deployed version you need to make as many changes as the number of the dependencies your are using from this project.  This is cumbersome and error prone.
> It would be much better if all the modules where deployed with the same time-stamp if they where part of the same reactor (e.g. the start time of the reactor build and not the start time of the module build)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)