[
https://issues.apache.org/jira/browse/MNG-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Nord updated MNG-6274:
----------------------------
Description:
If you have a multi-module build with SNAPSHOT versions and either install or
deploy it to your local repository all of the modules have different timestamps.
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 dpeployed with the same
timestamp 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)
was:
If you have a multi-module build with SNAPSHOT versions and either install or
delpoy it to your local repository all of the modules have different
timestampts.
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 dpeployed with the same
timestamp 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)
> 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: Improvement
> Components: Artifacts and Repositories, core
> Affects Versions: 3.5.0
> Reporter: James Nord
>
> If you have a multi-module build with SNAPSHOT versions and either install or
> deploy it to your local repository all of the modules have different
> timestamps.
> 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 dpeployed with the same
> timestamp 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
(v6.4.14#64029)
