You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2024/02/15 21:19:00 UTC

[jira] [Updated] (MRESOLVER-497) Investigate possible solutions for build number diffs on deploy

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

Tamas Cservenak updated MRESOLVER-497:
--------------------------------------
    Description: 
The "snapshot freeze" is a common practice during development: simply use a timestamped snapshot as dependency version instead of "-SNAPSHOT" ending one to "freeze" given snapshot deploy.

This works for simple cases (one dependency, or "aligned" reactor).

But take a look at Resolver itself: it has new-old and added-gone-readded modules, and their build numbers are different.

Problem is, that while timestamp is _same_ (deduced from session start), the build number is determined from remote repository (deploy target) state.

This makes "snapshot lock down" impossible on long(er) running projects, like Resolver itself is.

  was:
The "snapshot freeze" is a common practice during development: simply use a timestamped snapshot as dependency version instead of "-SNAPSHOT" ending one to "freeze" given snapshot deploy.

This works for simple cases (one dependency, or "aligned" reactor).

But take a look at Resolver itself: it has new-old and added-gone-readded modules, and their build numbers are different.

Problem is, that while timestamp is _same_ (deduced from session start), the build number is determined from remote repository (deploy target) state.


> Investigate possible solutions for build number diffs on deploy
> ---------------------------------------------------------------
>
>                 Key: MRESOLVER-497
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-497
>             Project: Maven Resolver
>          Issue Type: Task
>          Components: Resolver
>            Reporter: Tamas Cservenak
>            Priority: Major
>             Fix For: 2.0.0
>
>
> The "snapshot freeze" is a common practice during development: simply use a timestamped snapshot as dependency version instead of "-SNAPSHOT" ending one to "freeze" given snapshot deploy.
> This works for simple cases (one dependency, or "aligned" reactor).
> But take a look at Resolver itself: it has new-old and added-gone-readded modules, and their build numbers are different.
> Problem is, that while timestamp is _same_ (deduced from session start), the build number is determined from remote repository (deploy target) state.
> This makes "snapshot lock down" impossible on long(er) running projects, like Resolver itself is.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)